USASpending.gov

get_agency_overview

Read-only

Get descriptive information for an agency: name, mission, website, data notes and DEF codes. It has no dollar figures; for spending use get_agency_obligations_by_award_category() (split by award type) or get_agency_budgetary_resources() (obligations and outlays by year).

toptier_code is the 3- or 4-digit agency code (e.g. '097' for DoD,
'075' for HHS, '080' for NASA). Shorter inputs like '97' are left-padded
to '097' automatically. Get valid codes via list_toptier_agencies().

fiscal_year defaults to the last completed fiscal year, not the current
one (USAspending's own default). 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_overview"
  }
}

Input Schema

Name	Required	Description	Default
`fiscal_year`	No
`toptier_code`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's job is added context, which it delivers: the non-obvious fiscal_year default is the last completed year rather than the current one, and short codes are silently left-padded. Those two behaviors would otherwise surprise an agent interpreting results.

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 paragraphs, front-loaded with what the tool returns and what it does not, followed by parameter guidance. Nearly every sentence earns its place, though 'The answer always carries fiscal_year' is somewhat redundant given an output schema exists.

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 supplies everything needed to call it correctly: scope limits, parameter format with examples, the default-value trap, and where to get valid inputs. Return value structure is left to the output schema, as appropriate.

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 coverage is 0%, so the description must carry all parameter meaning, and it does: toptier_code is defined as a 3- or 4-digit agency code with concrete examples ('097' DoD, '075' HHS, '080' NASA), padding normalization is documented, and fiscal_year's default semantics are explained. This is meaning the schema cannot supply.

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 ('Get descriptive information for an agency') and enumerates exactly what comes back (name, mission, website, data notes, DEF codes). It explicitly bounds the scope ('It has no dollar figures') and names the two sibling tools that handle spending, so an agent can distinguish it from get_agency_obligations_by_award_category and get_agency_budgetary_resources without opening any schema.

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?

Gives an explicit when-not plus alternatives: for spending, use get_agency_obligations_by_award_category() for award-type splits or get_agency_budgetary_resources() for obligations/outlays by year. It also routes to list_toptier_agencies() for obtaining a valid code, so the prerequisite step is spelled out.

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.