Skip to main content
Glama

BRAINIAC Procurement Intelligence

Get US agency spend

procurement-intelligence_us-agency-spend
Read-onlyIdempotent

Retrieve award spending data for a US federal agency from USAspending by agency ID. Price $0.05 USDC. POST /api/v1/procurement-intelligence/us/agency-spend. An unpaid call returns the x402 payment terms and does not run.

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": {
      "agencyId": "<agencyId>"
    },
    "name": "procurement-intelligence_us-agency-spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
agencyIdYesagencyId, string. Required.
fiscalYearNofiscalYear, integer, from 2000 to 2099. Optional.

Output Schema

NameRequiredDescriptionDefault
inputNoinput. Object.
sourcesNosources. Array.
agencySpendNoagencySpend. Null.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the description correctly does not repeat them. Instead it adds what they cannot: a concrete cost ($0.05 USDC), the x402 payment protocol, and the precise fallback behavior for an unpaid call (returns payment terms, does not run) — exactly the operational context an agent needs before invoking a paid endpoint.

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?

Four short sentences, front-loaded with purpose, then cost, transport, and failure mode — each sentence carries distinct information. The raw path '/api/v1/procurement-intelligence/us/agency-spend' is the weakest element, since the POST verb is the only useful part of it for an agent.

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?

An output schema exists, so return values need no explanation, and the description covers cost, protocol, and unpaid-call behavior. It could go further on what 'spending' means (obligations vs outlays) or the granularity returned, but nothing essential to calling it correctly is missing.

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%, so both agencyId and fiscalYear are already documented in the schema and the baseline applies. The description reinforces that lookup is keyed by agency ID but adds no format, identifier-source, or fiscalYear defaulting detail beyond the schema.

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 description names a specific verb and resource ('Retrieve award spending data for a US federal agency from USAspending') and pins the key ('by agency ID'), which is enough to separate it from search-style siblings like us-awards-search. It stops short of explicitly contrasting itself with those siblings, so it lands just below the top.

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 only implied: the agent can infer this is the per-agency aggregate lookup rather than a search, but there is no explicit 'use this when / use X instead' guidance. The payment note is the only condition stated (unpaid calls return terms and do not execute).

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