Skip to main content
Glama
lzinga

US Government Open Data MCP

query_fiscal_data

Read-only

Select fields, filter, sort, and paginate U.S. Treasury fiscal data from endpoints like debt to the penny.

Instructions

Query the U.S. Treasury Fiscal Data API. Supports field selection, filtering, sorting, and pagination.

Filter operators: eq (equal), gt, gte, lt, lte, in. Example filter: 'record_date:gte:2024-01-01' Example sort: '-record_date' (descending) Multiple filters: 'country_currency_desc:in:(Canada-Dollar,Mexico-Peso),record_date:gte:2024-01-01'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYesThe API endpoint path, e.g. '/v2/accounting/od/debt_to_penny'
fieldsNoComma-separated list of field names to return. If omitted, all fields are returned. Example: 'record_date,tot_pub_debt_out_amt'
filterNoFilter expression. Format: field:operator:value. Multiple: field1:op1:val1,field2:op2:val2. Example: 'record_date:gte:2024-01-01,security_type_desc:eq:Treasury Bills'
sortNoComma-separated list of fields to sort by. Prefix with '-' for descending. Example: '-record_date'
page_numberNoPage number (1-indexed). Default: 1
page_sizeNoNumber of records per page (1-10000). Default: 100
Behavior4/5

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

The description explains supported operations (field selection, filtering, sorting, pagination) and provides filter operators with examples. The readOnlyHint annotation already signals no destructive side effects. No contradictions, and the description adds useful context beyond annotations.

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?

The description is concise (4 sentences), each sentence serving a purpose: purpose, capabilities, and examples. No redundancy or unnecessary information.

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?

The tool is simple (query with parameters), and the schema covers all parameters. The description adds examples and operators. While it does not mention error handling or rate limits, it is reasonably complete for a query tool with good schema coverage.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by providing concrete filter and sort syntax examples (e.g., 'record_date:gte:2024-01-01', '-record_date'), clarifying usage beyond the schema's property descriptions.

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 'Query the U.S. Treasury Fiscal Data API', specifying the exact resource and action. It distinguishes from sibling tools that target different data sources (e.g., BEA, BLS) by naming the specific API.

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?

The description implicitly indicates the tool is for querying Treasury fiscal data, but it does not explicitly state when to use it versus alternatives or when not to use it. However, the name and description are clear enough for an agent to select appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lzinga/us-gov-open-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server