Skip to main content
Glama

BRAINIAC Procurement Intelligence

Get US recipient profile

procurement-intelligence_us-recipients-profile
Read-onlyIdempotent

Retrieve recipient details from USAspending by recipient ID. Price $0.05 USDC. POST /api/v1/procurement-intelligence/us/recipients/profile. 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-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipientIdYesrecipientId, string. Required.

Output Schema

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

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 readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely non-structured behavior: the $0.05 USDC price and the x402 flow where an unpaid call returns payment terms and does not execute — critical for an agent to avoid misreading a failed run as an empty result. It does not discuss rate limits or throttling, keeping it short of a 5.

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?

Three short sentences, front-loaded with the purpose, then cost, then payment behavior. There is no padding. The raw POST path is of marginal value to an agent but is short enough not to bloat the definition.

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?

The tool is simple (one required parameter, output schema present so return values need no description), and the definition covers purpose, cost, and the non-obvious unpaid-call behavior. What remains unsaid — result shape, error semantics beyond payment — is either covered by the output schema or minor at this complexity.

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?

With a single parameter at 100% schema description coverage, the schema already carries the burden of documenting recipientId. The description only restates 'by recipient ID', adding no format, source, or example detail beyond the schema, which matches the baseline 3 for fully-covered schemas.

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 gives a specific verb and resource: 'Retrieve recipient details from USAspending by recipient ID.' That is unambiguous about what the tool returns and on what key. It does not explicitly contrast with sibling endpoints such as us-recipients-awards, but the resource noun 'profile' versus 'awards' is a reasonably clear differentiator.

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: an agent can infer it should call this when it already holds a USAspending recipient ID. There is no explicit when-to-use statement, no mention of which sibling to prefer for award history versus profile data, and no prerequisite guidance beyond the payment note.

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