Skip to main content
Glama

BRAINIAC Procurement Intelligence

Get US recipient awards

procurement-intelligence_us-recipients-awards
Read-onlyIdempotent

Retrieve award history for a US recipient from USAspending by recipient ID. Price $0.05 USDC. POST /api/v1/procurement-intelligence/us/recipients/awards. 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": {
      "recipientId": "<recipientId>"
    },
    "name": "procurement-intelligence_us-recipients-awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 100. Required.
recipientIdYesrecipientId, string. Required.

Output Schema

NameRequiredDescriptionDefault
inputNoinput. Object.
totalNototal. Number.
awardsNoawards. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new behavior the annotations cannot express: a $0.05 USDC price, the POST endpoint, and the fact that an unpaid call only returns x402 payment terms without executing — valuable for an agent that might otherwise treat a non-result as a failure.

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?

Three short sentences, each carrying distinct information: purpose, price, endpoint, and payment-gate behavior. Nothing is repeated from the schema or title, and the core purpose is front-loaded.

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 a rich annotation set, a 100%-documented two-parameter schema, and an output schema present, the description covers what the schema cannot: pricing and the x402 payment precondition. It does not say anything about result volume or ordering behavior, which is a minor gap given an output schema exists.

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% for both parameters, so the baseline is 3. The description adds only that recipientId is a USAspending recipient identifier; it says nothing about the limit parameter or paging semantics beyond what the schema already declares.

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 states a specific verb and resource — 'Retrieve award history for a US recipient from USAspending by recipient ID' — which is far more precise than the title alone. It implicitly distinguishes itself from award-search siblings by being recipient-scoped, but never names an alternative, so the differentiation is inferential rather than explicit.

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: 'by recipient ID' signals that a USAspending recipient identifier is a prerequisite, and the 'unpaid call returns x402 payment terms' line implies a payment-funded workflow. There is no statement of when to prefer this over the awards-search or recipient-profile siblings, and no exclusions or prerequisites spelled out.

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