USASpending.gov

autocomplete_recipient

Read-only

Find recipient names by partial name or UEI/DUNS.

This is a recipient-name lookup; it does not supply the recipient hash
for get_recipient_profile() or new_awards_over_time(), and its UEI/DUNS
fields may be null. Pass a returned name to search_recipients(): use
its 'id' hash for profiles/trends, and the UEI (or legacy DUNS) from
the parent (-P) row for get_recipient_children().

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": {
      "search_text": "<search_text>"
    },
    "name": "autocomplete_recipient"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`search_text`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond that: UEI/DUNS fields may be null and no recipient hash is returned. It does not mention pagination or what an empty result looks like, so it stops 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 sentences, front-loaded with the core purpose, then the negative scope, then the routing guidance. Slightly dense and line-broken mid-sentence, but every clause carries information.

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 not be explained, and the description focuses on the real hazard: the missing hash and nullable UEI/DUNS. The remaining gap is the unmentioned limit parameter and behavior on no matches.

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 0%, and the description clarifies that search_text accepts a partial name or a UEI/DUNS identifier, which is genuinely useful. However, the 'limit' parameter and its default of 10 are never mentioned, so the description only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource ("Find recipient names") plus the two match modes (partial name, UEI/DUNS). The second sentence explicitly states what the tool does NOT return (the recipient hash), which separates it from get_recipient_profile and new_awards_over_time.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the downstream step explicitly: pass a returned name to search_recipients(), use the 'id' hash for profiles/trends, and use the UEI or legacy DUNS from the -P row for get_recipient_children(). That is a concrete when-to-use-this-then-that chain with named alternatives, not an implication.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All USASpending.gov tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.