Skip to main content
Glama
Sign In

GovCon API

by io.github.govconapi
OverviewDiscussionsAdmin

Get one record

get
Read-onlyIdempotent

Fetch one record by its ID. IDs come from search results or resolve. (Pro) needs the Pro plan.

- opportunity: notice_id from search(opportunities)
- contract (Pro fields), contract_modifications, contract_vehicle, recompete (Pro): a PIID from search(contracts)
  or search(recompetes). contract_vehicle is the IDIQ or schedule the contract was ordered under
- vehicle, vehicle_holders (Pro): a vehicle PIID from search(vehicles) or get(contract_vehicle)
- entity: a UEI (12 characters) or CAGE code (5); company_profile, company_awards, company_peers, vendor_risk
  (all Pro), prime_subawards, prime_relationships: a UEI from resolve(company)
- subaward: subaward_sam_report_id from search(subawards)
- protests_on_solicitation (Pro): a solicitation number from an opportunity or contract
- wage_determination: wd_id from search(wage_determinations)
- office: office_code from search(offices)
- organization, organization_relationships: organization_id from resolve(organization);
  options.direction = children or ancestors for relationships
`options` takes the record's extra arguments: company_awards {limit, offset, sort_by, sort_order},
vehicle_holders {limit}, contract_modifications {limit, offset}, organization_relationships {direction}.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
optionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds genuinely new behavioral context beyond the annotations: per-kind Pro plan gating and the nested options contract (e.g. organization_relationships direction). It does not add rate-limit or pagination caveats, but the additions it does make are substantive.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by a scannable per-kind bullet list; for 20 enum values this density is justified. Minor redundancy in repeated '(Pro)' markers and the options recap, but nothing wasted overall.

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

Completeness5/5

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

An output schema exists, so return values need not be explained. Given that, the description covers the remaining gaps an agent needs: ID provenance per kind, plan gating, and per-kind options. Nothing essential for correct invocation is missing.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: it maps each `kind` enum value to the specific ID format expected (PIID, UEI 12 chars, CAGE 5, wd_id, office_code) and documents the `options` payload per kind (company_awards {limit, offset, sort_by, sort_order}, vehicle_holders {limit}, etc.). This far exceeds what the schema conveys.

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?

States a specific verb and resource ('Fetch one record by its ID') and implicitly contrasts with siblings that return many records (search) or map names to IDs (resolve). An agent can immediately tell this is the single-record retrieval tool in the family.

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

Usage Guidelines5/5

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

The description explicitly tells the agent where each ID comes from ('IDs come from search results or resolve') and enumerates the correct ID source per kind, e.g. notice_id from search(opportunities), a UEI from resolve(company). It also flags which kinds require the Pro plan, giving concrete when-to-use and prerequisite guidance.

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

All GovCon API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources