Skip to main content
Glama

BRAINIAC Procurement Intelligence

Search US awards

procurement-intelligence_us-awards-search
Read-onlyIdempotent

Search federal contract awards from USAspending with filtering by keyword, recipient, agency, and fiscal year. Price $0.05 USDC. POST /api/v1/procurement-intelligence/us/awards/search. An unpaid call returns the x402 payment terms and does not run.

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": "procurement-intelligence_us-awards-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 100. Required.
keywordNokeyword, string. Optional.
agencyIdNoagencyId, string. Optional.
fiscalYearNofiscalYear, integer, from 2000 to 2099. Optional.
recipientIdNorecipientId, string. Optional.

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?

Adds substantial information beyond the annotations: a concrete price ($0.05 USDC), the HTTP endpoint, and the critical behavior that an unpaid call returns x402 payment terms without executing. That payment-gate disclosure is exactly the kind of context annotations cannot carry. It stops short of describing pagination, result caps, or response shape.

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 with the purpose front-loaded, followed by cost, endpoint, and payment failure mode. No filler; the raw endpoint path is mildly technical but useful for debugging. Size is well matched to a five-parameter search tool.

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?

An output schema exists, all five parameters are documented, annotations cover the read-only/idempotent safety profile, and the description closes the remaining gap by explaining the pay-per-call requirement and unpaid-call behavior. Nothing essential to a correct invocation 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 each parameter is already documented in structured form. The description enumerates the same filter set generically and omits limit and the ID formats (agencyId, recipientId), adding little semantic detail beyond the schema; baseline 3 is appropriate.

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 specific verb and resource ('Search federal contract awards from USAspending') plus the filter dimensions, which is far more informative than the title alone. It does not explicitly distinguish itself from close siblings such as us-recipients-awards or us-agency-spend, so the agent must infer boundaries from the 'all awards, filterable' framing.

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 the listed filters (keyword, recipient, agency, fiscal year) rather than stated. There is no explicit when-to-use guidance, no exclusions, and no mention of the sibling tools that would be better for recipient- or agency-centric rollups.

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