Skip to main content
Glama

X420 agent services

x420_gov_usaspending-awards

Read-onlyIdempotent

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. Price: $0.05 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: count, has_more, awards[{award_id, recipient, amount_usd, awarding_agency, start_date, end_date, description, url}].

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 observed

TDQS

A3.8/5.0
Behavior5/5

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

The annotations only say readOnly/openWorld/idempotent/non-destructive; the description discloses the far less obvious fact that this hosted variant does NOT return the deliverable and instead returns payment instructions, then spells out the exact x402 handshake (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE). It also gives the price ($0.05 USDC on Base), the network, and the local-server alternative with a wallet key. This is behavior an agent could not otherwise infer and directly prevents a failed invocation loop.

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 purpose is correctly front-loaded, but the body is padded: 'Source: USAspending.gov' repeats the opening sentence, and the 'Not professional, legal, insurance, engineering, medical, financial or tax advice' disclaimer consumes a full sentence without helping an agent invoke the tool. The payment and deliverable details do earn their place, so the waste is partial rather than systemic.

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 paid, hosted proxy tool this is nearly complete: the payment flow, the alternative local-mode, and the exact deliverable field list (count, has_more, awards[...]) are all spelled out, which compensates for the absence of an output schema. Minor omissions remain, such as how has_more interacts with the limit cap and what an error/failed-payment response looks like.

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%, so every parameter is already self-documented with defaults and examples. The description adds only light corroboration (agency filtering, fiscal year, the four award types, default sort by amount); it introduces no syntax, enum, or constraint information beyond the schema. Baseline 3 is appropriate when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource: keyword search of US federal contracts, grants, loans or IDVs, with fiscal-year and agency scoping, from USAspending.gov. That is far more specific than a restatement of the name. It stops short of distinguishing itself from adjacent federal-data siblings such as x420_gov_federal-register, so an agent must infer that this tool covers spending/award records and not regulatory documents.

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?

Usage is implied rather than stated: keyword plus optional agency and fiscal-year filters make the intended query shape obvious, and 'free, no key' signals the tradeoff versus other sources. There is no explicit when-to-use/when-not statement and no named alternative for other award-related questions, so an agent gets context but no routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources