Skip to main content
Glama

US Treasury Auctions Payment Quote

treasury_auctions_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/treasury/auctions (base $0.003; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?type=bill|note|bond&status=upcoming|recent. US Treasury auctions for bills, notes or bonds. GET type=bill|note|bond&status=upcoming|recent. Each auction: CUSIP, term, announcement, auction and issue dates, offering amount. Recent auctions add high yield, bid-to-cover and allotments. Sources: TreasuryDirect auctions JSON API and the Fiscal Data Treasury securities auctions dataset. Not affiliated with or endorsed by the U.S. Treasury. Not investment advice. Bad input or an unavailable source: Not charged. 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 be

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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), yet the description adds substantial behavior: price ($0.003), the x402 v2 payment flow, the fact it never performs the underlying fetch or payment, per-chain error-charging rules, and non-affiliation/not-advice disclaimers. It is dense and the final clause is truncated mid-sentence ('HTTP status be'), which blunts the otherwise strong disclosure.

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

Conciseness2/5

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

The text is redundant and poorly front-loaded after the first sentence: the GET query string and the 'USDC on Base or Polygon' phrase each appear more than once, and payment/error rules plus disclaimers are packed into run-on sentences. The definition also ends mid-word, indicating the content was cut off rather than curated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description carries the full burden, and it does cover price, payment protocol, returned fields and error-charging policy. Gaps remain: the shape of the quote response itself is never described, the sibling relationship is unaddressed, and the truncated tail leaves a stated exception list incomplete.

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?

The input schema has zero parameters, so the baseline is 4, and the description does go further by naming the downstream query semantics (type=bill|note|bond and status=upcoming|recent) with concrete allowed values. However, it never clarifies whether these are arguments to this tool or paths encoded in the quoted URL, and the same query string is restated twice without added meaning.

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 opening sentence states a specific verb and resource ('Returns the payment terms for .../treasury/auctions') and immediately draws the critical line 'this tool never runs the check or pays', which distinguishes it from a data-fetching sibling. It also names the domain (US Treasury auctions for bills, notes or bonds), separating it from treasury_debt_quote and treasury_yield_curve_quote. It loses a point because the bulk of the text then describes auction payload fields the tool does not itself return, muddying what the tool actually produces.

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?

Usage is implied rather than stated: the agent can infer it should call this when it needs US Treasury auction data and is willing to pay the quoted terms. There is no explicit when-to-use/when-not guidance versus the treasury_* siblings, and no statement of what to do after receiving the quote (e.g. settle the 402, then re-request).

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.