Skip to main content
Glama

get_agency_awards

Read-only

Get one obligation total and transaction count for an agency's awards in a fiscal year.

The total covers ALL award types together (contracts, IDVs, grants,
loans, direct payments, other), so for most civilian agencies it is far
larger than contract spending (VA FY2026: $313B here vs $84B contracts).
For the split by award type use get_agency_obligations_by_award_category().
toptier_code is auto-padded to 3 digits if a shorter numeric value is
supplied.

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_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiscal_yearNo
toptier_codeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark this as read-only, non-destructive, and open-world. The description adds useful behavioral context beyond that: the aggregate includes every award type, fiscal_year defaults to the last completed fiscal year rather than the current one, and the response always includes fiscal_year.

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?

The primary purpose and key caveat are front-loaded, and the alternative tool is named early. The VA comparison is illustrative but somewhat verbose; it earns its place by clarifying aggregate scope, though it could be tightened.

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?

The tool has annotations covering safety and an output schema, so return formatting does not need explanation. The description provides the aggregation scope, default behavior, alternative routing, and parameter padding needed to call and interpret the tool correctly.

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 must carry parameter meaning, and it adds two important semantics: toptier_code is auto-padded to three digits when shorter, and fiscal_year defaults to the last completed fiscal year. It still leaves some ambiguity about the exact expected format/domain of toptier_code, but it is substantially more informative than the bare schema.

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 description states a specific verb and resource: return an agency's obligation total and transaction count for awards in a fiscal year. It also clarifies that the total aggregates all award types, which separates it from sibling tools focused on narrower categories.

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 explicitly routes users to get_agency_obligations_by_award_category() when they need a breakdown by award type. It also warns that the aggregate total is much larger than contract spending, which prevents incorrect use for contract-only questions.

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.