Skip to main content
Glama

Treasury Debt Payment Quote

treasury_debt_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/treasury/debt (base $0.01; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET with no parameters. U.S. Treasury debt to the penny: total, held by the public, and intragovernmental, with the 1-day, 30-day and 1-year change, plus the Daily Treasury Statement Treasury General Account (TGA) operating-cash balance and its daily change. No parameters. Source: api.fiscaldata.treasury.gov. debtUsd is USD. cashUsdMillions is millions of USD. Not a forecast. USDC on Base or Polygon. On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (native USDC), a request is settled only when it succeeds (HTTP status below 400). Failed requests are not charged.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds material behavioral context beyond them: the $0.01 base price, the payment protocol, the settlement/charging rules per chain (Base errors not charged, Solana/XRPL refusals may still be charged, Polygon settled only on success), and the upstream source. It is rich, but repeated 'USDC on Base or Polygon' statements and a multi-chain charging discussion that partially conflicts with the narrower chain list make it less than crisp.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core facts are front-loaded, but the text repeats itself ('No parameters' twice, 'USDC on Base or Polygon' three times) and mixes the pricing/payment-settlement tail with the return-value description, adding length without new 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?

There is no output schema, so the description must describe return values, and it does: field-level content (total, public, intragovernmental, change windows, TGA cash balance) plus units (debtUsd in USD, cashUsdMillions in millions) and the source. What remains undescribed is the response envelope and whether the quote itself or the underlying data is returned, a minor gap given no output schema.

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?

There are zero parameters, so the baseline is 4; the description confirms 'No parameters' and reinforces this with the HTTP method. No additional per-parameter meaning is needed or possible.

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?

The description names the specific resource (U.S. Treasury debt to the penny: total, public holdings, intragovernmental, 1-day/30-day/1-year changes, plus the TGA operating-cash balance) and distinguishes this from its sibling treasury_yield_curve_quote by dataset. It also states the tool's role clearly: it returns payment terms and 'never runs the check or pays.' Only the slightly ambiguous opening ('Returns the payment terms for ...') before the data description keeps it from a 5.

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

Usage Guidelines3/5

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

It tells the agent the mechanics of use ('GET with no parameters', pay the 402 over HTTP with x402 v2) and that the tool itself does not perform the fetch or payment, which implies a quote-then-pay flow. However, it never names alternatives (e.g., treasury_yield_curve_quote) or states when not to use it, so the routing guidance is only implied.

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.