Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Newest US federal contract awards above an amount in one call (USAspending): recipient, amount, awarding agency, last mo

gov_contracts
Read-onlyIdempotent

Newest US federal contract awards above an amount in one call (USAspending): recipient, amount, awarding agency, last modified, description, award id (min_amount default 1000000, days 1..7, count up to 50). One poll replaces watching federal spending. Pay per call $0.002 USDC on Base via x402.

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": "gov_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo1 to 7
countNoup to 50
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements
min_amountNoUSD, default 1000000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the genuinely non-obvious behavior: this is a paid endpoint at $0.002 USDC on Base via x402, and one call replaces repeated polling. It does not state rate limits, result ordering tie-breaks, or what happens when the payment is absent beyond what the x_payment schema note says.

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 resource and filter, then the returned fields, then the payment terms — a sensible order for an agent scanning for fit. It is dense with nested parentheses but no sentence is filler; the payment line in particular earns its place.

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?

With no output schema, the description compensates by listing the fields returned, so the agent knows what comes back. It covers cost and the x402 handshake sufficiently (the schema note explains omitting x_payment on the first call). The main residual gap is the error/failure behavior when payment is rejected or no awards match.

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 description coverage is 100%, and the parenthetical merely restates the same defaults already in the schema ('min_amount default 1000000, days 1..7, count up to 50'). No extra semantic detail is added, such as whether days is calendar days back from now or whether count caps at the API limit. Baseline 3 applies since the schema carries the burden.

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?

States a concrete resource ('US federal contract awards', sourced from USAspending) with an explicit filter (above an amount) and enumerates the returned fields (recipient, amount, awarding agency, last modified, award id). An agent can distinguish this from siblings like eu_tenders or federal_register on resource and jurisdiction, though the description never names an alternative directly.

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 by 'One poll replaces watching federal spending', which signals a polling/monitoring use case, and the parenthetical supplies operating bounds (days 1..7, count up to 50, default min_amount). There is no explicit when-not guidance and no routing to alternatives such as eu_tenders for non-US awards or federal_register for rulemaking documents.

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