Skip to main content
Glama
govconapi

io.github.govconapi/govconapi

Official

Get Vehicle Holders

get_vehicle_holders
Read-onlyIdempotent

Check eligibility to bid on task orders by distinguishing vehicle holders from actual earners. Get awardee and earner counts plus related vehicle family PIIDs for compliance analysis.

Instructions

Get who holds a vehicle AND who's actually earning through it, two distinct populations, don't conflate them: a firm can hold a vehicle for years and earn nothing on it.

Award & Compliance tool, Pro only. The "can I even compete for this work" answer, on a multi-award vehicle, only holders can bid task orders.

- piid: vehicle's own PIID (from search_vehicles or get_contract_vehicle)
- limit: max 250

Returns `awardees` (hold the vehicle) and `earners` (have actually been paid through
it) as separate lists with counts (`awardee_count`/`earner_count`), on a real
multi-award vehicle these can be wildly different (e.g. 1,596 awardees, 2 earners),
which is the whole point of the distinction. Each entry's `recipient_uei` chains into
Capture/Teaming tools. Also returns `vehicle_family.piids`: this rolls up EVERY
related PIID under the same vehicle family, not just the one you asked for, so
`awardee_count` reflects the whole family, not a single order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
piidYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, etc.), the description discloses behavioral details: it returns separate lists with counts, rolls up related PIIDs via vehicle_family.piids, and notes the 'Pro only' access restriction. These are meaningful behaviors not captured by annotations.

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

Conciseness2/5

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

The description is verbose and repetitive, restating the holder/earner distinction multiple times and repeating the same return-value explanation. It could be condensed significantly without losing meaning, making it less efficient for agents to parse.

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

Completeness4/5

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

Despite having an output schema (not shown), the description thoroughly explains the return structure (awardees, earners, counts, vehicle_family.piids) and the use case. It is complete enough for an agent to understand when and how to invoke the tool correctly.

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

Parameters5/5

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

The schema provides only types and defaults, but the description explains that 'piid' is the vehicle's own PIID (from specific sources) and that 'limit' has a max of 250, adding crucial context. This fully compensates for the schema's lack of parameter descriptions.

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

Purpose5/5

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

The description clearly states the tool retrieves vehicle holders and earners as distinct populations, emphasizing not to conflate them. It identifies the specific resource (vehicle) and differentiates from similar tools by highlighting the unique holder-vs-earner distinction.

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

Usage Guidelines4/5

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

Provides contextual guidance such as 'Award & Compliance tool, Pro only' and 'only holders can bid task orders,' indicating when this tool is relevant. However, it does not explicitly state when to prefer this over sibling tools like get_vehicle or search_vehicles, though the holder/earner distinction implies its niche.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/govconapi/govconapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server