Skip to main content
Glama

Find contract vehicles for an industry

vehicle_match
Read-onlyIdempotent

For 6-digit NAICS codes (and an optional agency): the shared contract vehicles (GWACs, multiple-award IDIQs, GSA Schedule, BPAs) carrying last complete year's contract money in those codes, the share through each and who each is reserved for (read from its name).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "naics": "<naics>"
    },
    "name": "vehicle_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
naicsYesOne or more 6-digit NAICS codes, e.g. ["541511", "541512"].
agencyNoAn agency to limit to, by name or code, e.g. "Department of Veterans Affairs" or "036".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "vehicle_matchDictOutput",
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description does add real context beyond that: the data window is 'last complete year's contract money', results include the share through each vehicle, and the 'reserved for' field is explicitly derived from the vehicle's name — a useful caveat about a heuristic. It stops short of describing aggregation across multiple codes or result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, but the grammar is a fragment ('For 6-digit NAICS codes ...: the shared contract vehicles ... the share through each and who each is reserved for'), which forces a re-read. The key scope constraint is front-loaded, but the output list is buried in a trailing clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two fully-documented parameters, an output schema, and rich annotations, most structured burden is already carried elsewhere. The description covers scope, time window, and the name-derived reservation caveat, but leaves open how multiple NAICS codes combine and whether agency filtering changes the share calculation — gaps an agent could plausibly hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and both parameters carry their own descriptions with examples, so the schema does the heavy lifting. The description only echoes the '6-digit' requirement and the optionality of agency; it adds no meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely — shared contract vehicles (GWACs, multiple-award IDIQs, GSA Schedule, BPAs) — and the scoping inputs (6-digit NAICS, optional agency). It is clearly distinct from award-level or bid-portal siblings, but it never names an alternative sibling, so an agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative (e.g. award_prices for dollar detail, find_bid_portals for solicitation sources). The 'For 6-digit NAICS codes' phrasing hints at the entry condition but leaves the choice between tools to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources