Skip to main content
Glama

x420_gov_usaspending-awards

Search US federal contracts, grants, loans, or IDVs by keyword and fiscal year, optionally filter by agency, and return award details as JSON.

Instructions

Federal awards search (USAspending): Keyword search of US federal contracts, grants, loans or IDVs for a fiscal year, optionally filtered to one awarding agency, sorted by amount, from the USAspending.gov API (free, no key). Source: USAspending.gov. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.05 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: count, has_more, awards[{award_id, recipient, amount_usd, awarding_agency, start_date, end_date, description, url}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"keyword":"roofing","award_type":"contracts","fiscal_year":"2026","limit":"1"}.

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": {
      "keyword": "<keyword>"
    },
    "name": "x420_gov_usaspending-awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1–25 (default 10)
agencyNoawarding top-tier agency name, e.g. Department of Defense (default: any)
keywordYessearch term, e.g. roofing
award_typeNocontracts (default), grants, loans or idvs
fiscal_yearNoUS fiscal year (default current)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing that each call costs $0.05 USDC settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money), that the API itself is free and keyless, and that the response includes a signed receipt and settlement transaction. This also explains why readOnlyHint is false despite the operation being a search — the payment settlement is a side effect — so there is no contradiction.

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

Conciseness3/5

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

The core purpose and cost are front-loaded, which is good, but the text is dense with boilerplate — a lengthy non-advice disclaimer and a full inline return-field listing sit in the same block as the selection guidance. That said, since there is no output schema, the return listing earns its place more than the disclaimer does.

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 paid, open-world external API call with no output schema, the description covers everything an agent needs: data source, cost and settlement mechanism, credential requirement, response shape with named fields, and a worked example input. Nothing material is left unspecified.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: it repeats the award_type and fiscal_year options, notes that the agency filter targets a single top-tier awarding agency, and supplies a concrete example input that shows realistic value formatting for four of the five parameters.

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 opens with a specific verb and resource ('Keyword search of US federal contracts, grants, loans or IDVs'), names the source (USAspending.gov), and characterizes the scope (fiscal year, optional agency filter, sorted by amount). An agent can immediately tell this is a government award lookup tool rather than a spending analytics or regulatory-document tool.

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?

It specifies the required input (a keyword) and that filters are optional, which implies when the tool applies. However, it never names an alternative such as x420_spend_summary or x420_gov_federal-register, nor states when this tool is the wrong choice, leaving sibling routing to inference.

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