Skip to main content
Glama

get_agency_sub_agencies

Read-only

List the subordinate (subtier) organizations of a toptier agency.

Returns each sub-agency with its obligations, transaction count, and
new-award count for the given fiscal year. Useful for finding the
canonical subtier name to pass into search_awards() awarding_subagency.

sort accepts name, total_obligations, transaction_count, or
new_award_count (this endpoint has no outlay column; a former
'total_outlays' option was rejected by the API with HTTP 400).

fiscal_year defaults to the last completed fiscal year, not the current
one (USAspending's own default, which right after October 1 holds only a
few days of data). The answer always carries fiscal_year.

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": {
      "toptier_code": "<toptier_code>"
    },
    "name": "get_agency_sub_agencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNototal_obligations
limitNo
orderNodesc
fiscal_yearNo
toptier_codeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/no-destructive, so the description focuses on the non-obvious behavior: the fiscal_year default is the last completed fiscal year, not the current one, with an explanation of why (right after Oct 1 the current year holds only days of data). It also warns that a former 'total_outlays' sort option triggers HTTP 400 — exactly the kind of runtime gotcha annotations can't convey.

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 tight paragraphs, each front-loaded with its point: what it lists, how to use the result, sort constraints, then the fiscal_year gotcha. No filler sentences; even the parenthetical about total_outlays earns its place as a failure warning.

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 an output schema present, return-value explanation is not strictly needed, and the mutation/safety profile is covered by annotations. The description covers the fiscal-year and sort traps well; only the pagination parameters (page/limit/order) are left unexplained, which is a minor gap for a list tool.

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%, so the description must carry parameter meaning. It does a strong job on 'sort' (listing valid values and the rejected outlay option) and 'fiscal_year' (default semantics), but leaves page, limit, order, and toptier_code entirely undescribed — roughly half the parameters get no added meaning.

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 — listing subtier organizations of a toptier agency — and names exactly what is returned (obligations, transaction count, new-award count). It also distinguishes itself from the many get_agency_* siblings by describing its downstream use case.

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

Usage Guidelines4/5

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

Explicitly explains the intended use: finding the canonical subtier name to pass into search_awards() awarding_subagency, which tells the agent why to pick this over generic agency lookup tools. It stops short of naming a direct sibling alternative or stating when-not to use it.

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.