G2XGovCon MCPCreate G2X account

GOVCON MCP / TOOL REFERENCE / MARKET RESEARCH

Analyze a contract vehicle

g2x_vehicle_usage

What it does

Shows how a contract vehicle is used in G2X's award data — contract holders on record, task orders and money obligated on them — found by name, program acronym, solicitation number or vehicle ID. An exact IDV PIID or full CONT_IDV_ key instead reports that one award and its bounded orders. A task-order PIID or CONT_AWD_ key returns a correction with its recorded parent IDV key when available. These are partial figures: G2X's records may not list every holder, and they are not the vehicle's ceiling; the program office publishes both. Useful for deciding whether a vehicle matters in a lane.

Inputs

  • identifier (text, optional): The vehicle's name or program acronym as G2X lists it (e.g. "OASIS+"), its solicitation number, or the vehicle ID a previous answer named. A name that fits several vehicles returns them to choose from.
  • query (text, optional): Alias for identifier; identifier takes precedence.
  • vehicle (text, optional): Alias for identifier; identifier and query take precedence.
  • name (text, optional): Alias for identifier; identifier, query and vehicle take precedence.
  • candidate_cursor (text, optional): The opaque facts.candidate_cursor from a previous answer, up to 500 characters without whitespace, for the same vehicle name. It lasts 5 minutes; after that, omit it to start again.

What it returns

One answer: a title, named facts and a text body, plus notes on what the answer covers.

Try asking

How much work has gone through the OASIS+ vehicle, and who holds it?

AI and your account

  • Does not use G2X's own AI: your agent does any analysis with its own model.
  • Reads only: it changes nothing in your G2X account.

Next steps