USASpending.gov

get_recipient_children

Read-only

Get the child recipients (subsidiaries) of a parent recipient.

Pass the parent recipient's 12-character UEI (or legacy 9-digit DUNS).
Do NOT pass a recipient hash: the /recipient/children/ endpoint is the
one recipient endpoint keyed by UEI/DUNS, and it rejects hashes with
HTTP 400. Get the UEI from search_recipients() results (the 'uei' field
of the -P row) or from get_recipient_profile().

Returns the child recipients, each with its own -C suffixed recipient_id
hash usable with get_recipient_profile(). Useful for mapping corporate
structures (e.g. Lockheed Martin parent -> all its subsidiaries).

year: optional 'all', 'latest', or a fiscal year like 2026.

The upstream endpoint returns a JSON array; it is wrapped here as
{"results": [...], "total": N} to keep the dict-only response invariant.

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": {
      "uei_or_duns": "<uei_or_duns>"
    },
    "name": "get_recipient_children"
  }
}

Input Schema

Name	Required	Description	Default
`year`	No
`uei_or_duns`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already establish read-only and non-destructive behavior, and the description adds substantial extra context: the endpoint rejects hashes, returns child recipients with -C suffixed recipient_id hashes usable elsewhere, and wraps the upstream JSON array as {"results": [...], "total": N}.

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?

The description is front-loaded with the core action, then gives identifier constraints, return behavior, and year semantics. Every sentence contributes useful information and there is no redundant restatement of the schema.

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?

For a two-parameter read-only lookup with an output schema, the description is complete: it explains the required identifier format, the specific failure mode to avoid, the year options, and how returned child recipient hashes can be used.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It fully documents both parameters: uei_or_duns accepts a 12-character UEI or legacy 9-digit DUNS and explicitly not a hash, while year accepts 'all', 'latest', or a fiscal year such as 2026.

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?

States a specific verb and resource: getting child recipients (subsidiaries) of a parent recipient. It clearly distinguishes this from related recipient tools by naming search_recipients and get_recipient_profile as UEI sources.

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?

Explicitly says when to use it and what not to do: do not pass a recipient hash because this endpoint is keyed by UEI/DUNS and rejects hashes with HTTP 400. It also tells the agent where to obtain the required identifier.

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.