Skip to main content
Glama
Sign In
USAspending MCP Server

USAspending MCP Server

by haydentbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search USAspending Transactions

usaspending_search_transactions
Read-onlyIdempotent

Search federal spending transactions with custom filters to retrieve action dates, modifications, and amounts from USAspending.

Instructions

Search individual transaction records with USAspending AdvancedFilterObject filters. Use when award-level results are too aggregated and you need action dates, modifications, or transaction amounts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "usaspending_search_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoUSAspending AdvancedFilterObject. Common keys include time_period, keywords, agencies, recipient_search_text, award_type_codes, award_ids, naics_codes, psc_codes, and place_of_performance_locations. Specify an explicit time_period for time-sensitive analysis.
fieldsNoTransaction fields to return. Examples: Award ID, Mod, Recipient Name, Action Date, Transaction Amount, Awarding Agency, Award Type.
limitNoResults per page.
pageNoPage number to return.
sortNoTransaction Amount
orderNodesc
response_formatNoOutput format: markdown for readable summaries, json for raw structured data.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that it searches individual transaction records and mentions result fields, consistent with annotations. No contradictions.

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?

Two sentences directly addressing purpose and usage. No wasted words; front-loaded with the key verb and resource.

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?

Given the tool's complexity (7 params, nested objects) and lack of output schema, the description covers purpose and usage well but could elaborate on filter structure. Remains sufficient for most use cases.

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 71%. The description adds minimal param insight beyond the schema, though it does note to specify time_period for time-sensitive analysis. Baseline score of 3 is appropriate.

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 clearly states it searches individual transaction records and specifies the use case when award-level results are too aggregated, distinguishing from sibling tools like usaspending_search_awards.

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 says when to use: when award-level results are too aggregated and you need action dates, modifications, or transaction amounts. Provides clear context but no when-not-to-use.

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

Deploy Server

Other Tools