Skip to main content
Glama
GovCon API MCP

GovCon API MCP

Official

Get one record

get
Read-onlyIdempotent

Fetch a single federal procurement record by ID from prior search or resolve results, covering opportunities, contracts, entities, subawards, and related data.

Instructions

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: opportunity {attachments: true for the notice's files with names, sizes and download URLs}, company_awards {limit, offset, sort_by, sort_order}, vehicle_holders {limit, awardee_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. Addedv0.2.4

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 the safety profile is covered. The description adds genuine context beyond that: Pro-plan gating per kind and what extra data `options` unlocks (e.g. attachments with names, sizes, download URLs). It does not mention rate limits or what happens with an invalid ID, but those are secondary for a read-only fetch.

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?

Front-loaded with the one-line purpose, then a scannable per-kind list, followed by an `options` paragraph. It is dense but every line carries operational detail; a small deduction because the options sentence packs many kinds together and is harder to skim than the bulleted section.

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?

For a single-fetch tool with an output schema already describing return values, nothing essential is missing: ID provenance, per-kind requirements, Pro gating, and the extra-argument object are all covered. The description carries the full burden of the 0%-covered schema and does so completely.

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%, and the description fully compensates: it documents every enum value of `kind` with the expected ID source, gives format constraints (UEI 12 characters, CAGE 5), and explains the untyped `options` object per kind (limit/offset/sort/attachments/direction). This adds meaning far beyond the bare `anyOf` schema.

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 immediately distinguishes itself from siblings by naming where IDs come from (search results or resolve). An agent can tell this apart from search/resolve without opening the schema.

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?

Provides per-kind routing instructions: which ID to supply for each of the 20 kinds and which sibling tool produces it (e.g. notice_id from search(opportunities), UEI from resolve(company)). It also flags which kinds require the Pro plan, so the agent knows when the call may be unavailable.

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

Deploy Server

Other Tools