Govparse Government Data Gateway

govcon_award_search

Who has the government actually paid, for what, and how much? Search USAspending federal award history (contracts and assistance) by recipient name or UEI, awarding agency, NAICS prefix, CFDA number, amount range, and action-date window — competitor award research, incumbent lookup before a recompete, and grant-winner analysis in one call. [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`uei`	No	Recipient Unique Entity Identifier (SAM UEI), exact match.
`cfda`	No	CFDA / Assistance Listing number, exact match (assistance awards).
`kind`	No	contract \| assistance (grants, loans, direct payments). CSV for both.
`sort`	No	field:direction — amount \| action_date. Default 'amount:desc'.
`limit`	No	Max rows (default 25, cap 100).
`naics`	No	NAICS code prefix(es), CSV.
`agency`	No	Awarding agency or sub-agency name fragment. Example: 'defense'.
`offset`	No	Rows to skip, for paging.
`recipient`	No	Award recipient name fragment. Example: 'lockheed'.
`amount_max`	No	Maximum award amount in USD.
`amount_min`	No	Minimum award amount in USD.
`awarded_after`	No	Action date on or after (YYYY-MM-DD).
`awarded_before`	No	Action date on or before (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses pricing ($0.05/row) and the 'kind' parameter accepts 'contract' or 'assistance' with CSV for both. However, it does not mention behavior like result limits, pagination details beyond schema (offset/limit), or what happens with empty results.

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?

The description is a single paragraph that hooks with a question, then lists parameters and use cases, and ends with pricing. It is reasonably concise but slightly verbose; it could be tightened by removing the hook or merging sentences.

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?

For a tool with 13 parameters and no output schema, the description provides sufficient context to understand the tool's purpose, searchable fields, and typical use cases. It is adequate without being exhaustive.

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% with descriptions and examples for all parameters. The description adds overarching context (e.g., 'competitor award research') but does not add new meaning to individual parameters beyond what the schema already provides.

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 uses a specific verb ('Search') and resource ('USAspending federal award history'), clearly distinguishing from sibling tools like 'govcon_opportunity_search' (opportunities) and 'govcon_subaward_search' (sub-awards). It lists specific search dimensions (recipient, agency, NAICS, etc.) and use cases (competitor research, incumbent lookup, grant-winner analysis).

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?

The description explicitly mentions three use cases (competitor award research, incumbent lookup, grant-winner analysis) and implies the tool covers both contracts and assistance. However, it does not explicitly state when to use alternatives or provide exclusion criteria.

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

All Govparse Government Data Gateway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct domain and specific action (e.g., FDA approvals vs clearances vs recalls; firmstanding business360 dossier vs search vs screen). Even overlapping concepts like 'business360' vs 'business360_lookup' are distinguished by input (UUID vs name+state). No two tools appear to do the same thing.

Naming Consistency5/5

All tools use a consistent lowercase snake_case pattern with domain prefix (e.g., fda_*, firmstanding_*, fmcsa_*, govcon_*). Action words (search, lookup, screen, feed, stats) follow predictable usage. The naming is uniform and easy to parse.

Tool Count4/5

38 tools is on the higher end but appropriate for a comprehensive government data gateway spanning multiple agencies and datasets. Each domain has a reasonable number of tools (e.g., FMCSA: 7, OFLC: 6). Could potentially be trimmed slightly, but overall well-scoped for the stated purpose.

Completeness5/5

The tool surface covers the major government data sources comprehensively: FDA (approvals, clearances, recalls), FMCSA (carrier census, safety, insurance, etc.), FSIS, DOJ/OFLC, OSHA/EPA/DOL enforcement, SEC insider filings, clinical trials, VA facilities/opportunities/vendors, and federal contracting. No obvious gaps for the stated gateway purpose.

Resources

Need Help?