Skip to main content
Glama

Treasury Yield Curve Payment Quote

treasury_yield_curve_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/treasury/yield-curve (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 (latest published day), or ?date=YYYY-MM-DD. US Treasury daily par yield curve, 1-month to 30-year, plus 2s10s and 3-month/10-year spreads. Optional date=YYYY-MM-DD (default: latest day). Data credit: U.S. Department of the Treasury; not affiliated with or endorsed by the Treasury. Up to 30 minutes old. Informational only, no warranty; not advice. Bad input is refused before payment, not charged. If no curve exists for the date, it is refused and not charged; if any tenor returns data, the full price is 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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Rich disclosure beyond the read-only/idempotent annotations: base price $0.01, charge-on-failure rules differing per chain (Base errors uncharged, Solana/XRPL may charge), refusal-before-payment for bad input or missing curve, partial-tenor full-charge rule, and data freshness up to 30 minutes. It loses a point because the final settlement sentence is cut off mid-clause, leaving Polygon behavior unexplained.

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?

Key facts (payment terms, price, protocol) are front-loaded, but the text then sprawls through legal credit, warranty disclaimers, and per-chain settlement rules, repeats 'USDC on Base or Polygon' twice, and terminates mid-sentence. Several sentences do not earn their place in a definition this size.

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?

For a zero-parameter quote tool with no output schema, it covers pricing, protocol, freshness, and refunds well, but never describes the shape of the returned payment terms and ends truncated, so an agent cannot fully predict what it receives or how Polygon settlement resolves.

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?

The schema declares zero parameters, which would normally be a baseline 4, but the description advertises an optional date=YYYY-MM-DD query argument that does not exist in the input schema. That adds real meaning about the endpoint yet creates a mismatch an agent cannot resolve from structured fields.

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 resource (the treasury/yield-curve endpoint) and the output class (payment terms), and explicitly disclaims running the check or paying, which distinguishes it from a data-fetch tool. It is weakened by spending most of the text describing the underlying dataset rather than the quote behavior, so the quote-vs-data distinction takes a few sentences to settle.

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 explains how the returned terms are to be used (pay the 402 over HTTP with x402 v2, GET with no params or ?date=), which is actionable context. However, it never names a sibling to prefer or a condition under which to skip this tool, and the relationship to siblings like treasury_debt_quote or x402_check is left implicit.

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.