Skip to main content
Glama
Sign In

USASpending.gov

by com.1102tools
OverviewDiscussionsAdmin

get_federal_account_program_activities

Read-only

List program activity codes and names associated with a federal account.

The source lists distinct programs across all reported fiscal years; it
has no fiscal-year filter and includes no dollar amounts. fiscal_year is
retained for compatibility, but does not filter this list. The response
explicitly discloses any requested year that was not applied.

Retrieves source pages internally, up to 2,000 records, and reports whether
the list is complete. For single-year account resources and obligations,
use get_federal_account_fy_snapshot with the numeric account_id returned
by list_federal_accounts. get_agency_program_activities provides fiscal-year
program amounts for an agency, not for this individual federal account.

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": {
      "account_code": "<account_code>"
    },
    "name": "get_federal_account_program_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiscal_yearNo
account_codeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing that the source spans all reported fiscal years, contains no dollar amounts, paginates internally up to 2,000 records, reports completeness, and explicitly echoes any requested year that was not applied. That is exactly the behavioral context an agent needs before calling.

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?

Front-loaded purpose sentence, then caveats, then alternatives — good ordering and no filler. The closing pointer to list_federal_accounts' numeric account_id sits awkwardly next to this tool's string account_code and could momentarily confuse the reader.

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 described, and the description still covers limits, completeness signaling, and sibling routing. The only missing piece is guidance on the account_code value itself.

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

Parameters4/5

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

With 0% schema description coverage the description carries the full burden, and it resolves the tricky fiscal_year parameter (accepted for compatibility, ignored for filtering). The required account_code is never described in format or provenance, leaving one real 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?

Opens with a specific verb and resource: 'List program activity codes and names associated with a federal account.' It immediately distinguishes the resource scope (program activities for one federal account) from the sibling get_agency_program_activities and get_federal_account_fy_snapshot.

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 names alternatives and the conditions that select them: use get_federal_account_fy_snapshot for single-year resources/obligations, and get_agency_program_activities for agency-level fiscal-year amounts. It also warns that fiscal_year does not filter here, which prevents a common misuse.

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

All USASpending.gov toolsInspect
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.

Resources