govcon-feed

search_awards

Direct live search of US federal awards (USAspending.gov) by NAICS, agency, recipient, keyword, date range, and $ range. Use for ad-hoc lookups.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_awards"
  }
}

Input Schema

Name	Required	Description
`end`	No
`limit`	No	Default 50, max 200.
`naics`	No
`start`	No
`agency`	No
`keyword`	No
`maxAmount`	No
`minAmount`	No
`recipient`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 21, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It states 'Direct live search' implying real-time external API access, but fails to mention safety (read-only), rate limits, authentication, or data freshness.

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

Conciseness5/5

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

Two short, front-loaded sentences with no superfluous information, achieving high information density.

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

Completeness2/5

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

Despite 9 parameters and no output schema or annotations, the description omits return format, pagination details, error handling, and caveats about live external data latency.

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

Parameters2/5

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

Only 11% of parameters have schema descriptions (limit); description lists categories (naics, agency, keyword, date range, $ range) but provides no format, syntax, or examples for the 9 parameters. Falls short of compensating for low schema coverage.

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?

Description clearly states verb 'search', resource 'US federal awards (USAspending.gov)', and lists search dimensions (NAICS, agency, keyword, etc.). It differentiates itself from sibling tools which focus on competitor watching and change detection.

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

Usage Guidelines3/5

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

Says 'Use for ad-hoc lookups', giving a general usage context. However, no explicit guidance on when not to use it or alternatives, though siblings are unrelated.

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

All govcon-feed tools Inspect

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

Need Help?