Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

US Treasury fiscal snapshot in one call: total public debt outstanding to the penny (latest and previous day, change), d

us_treasury
Read-onlyIdempotent

US Treasury fiscal snapshot in one call: total public debt outstanding to the penny (latest and previous day, change), debt held by public and intragovernmental, and the latest average interest rates by security type (bills, notes, bonds, TIPS). days=1..30 returns a daily debt series. Pay per call $0.002 USDC on Base via x402.

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": "us_treasury"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo1 to 30, daily debt series
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: each call is billed $0.002 USDC on Base via x402, which an agent must know before invoking. It stops short of describing rate limits or failure modes for incomplete payment.

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?

Content is front-loaded: what data comes back first, then the days-series behavior, then the pricing note. It is a single dense sentence plus two short follow-ups with no wasted framing. Minor duplication with the title text is the only inefficiency.

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?

With no output schema, the description does the work of naming the returned figures, which is the right call for a data-snapshot tool. Payment mechanics and the first-call handshake are covered. Only return structure details (shape, ordering, freshness/timestamp) are left unspecified.

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 coverage is 100%, so both parameters are already documented, including the instruction to omit x_payment on the first call to receive pricing. The description restates days=1..30 as producing a daily debt series, adding modest clarity but no syntax or format detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource pair ('US Treasury fiscal snapshot') and enumerates the exact figures returned: total public debt to the penny, previous-day change, public and intragovernmental holdings, and average interest rates by security type. This is far more specific than the name alone. It does not explicitly differentiate itself from siblings, though the sibling list covers unrelated domains (weather, filings, npm), so the risk of confusion is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only conditional behavior conveyed is implicit in the payment sentence and the 'days=1..30 returns a daily debt series' clause, which tells the agent the parameter's effect but not when to pick this tool over anything else.

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.

Resources