Tanod MCP server

utilpeek: US Treasury par yield curve (daily, 1 Mo to 30 Yr)

treasury_yield_curve

Read-onlyIdempotent

Retrieve official US Treasury par yields for a chosen date, covering 1-month to 30-year maturities. Defaults to the current curve; dates without one return the nearest earlier published date.

Instructions

utilpeek: Get US Treasury yields: the daily par yield curve for a date. For SOFR, FX and oil too use get_macro_snapshot. Returns the official US Treasury daily par yield curve for a date (default: the latest): yields in percent from 1 Mo to 30 Yr (null where none was published); a date without a curve returns the nearest earlier one (adjusted: true). Informational only, not investment advice. Data: U.S. Treasury (public domain), cached up to 6 hours; no Treasury endorsement implied. A bad, pre-1990 or future date is a 422 (not charged); an upstream outage is a 503 (not charged). Typically under 0.1 s from cache; up to about 25 s when the Treasury feed is fetched (it is slow). Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/treasury-yield-curve-api.html

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Curve date YYYY-MM-DD (1990-01-02 to today). Default: the latest published curve. A date with no curve (weekend, holiday, not yet published) returns the nearest earlier one, with adjusted: true.

Output Schema

TableJSON Schema

Name	Required	Description
`date`	No
`note`	No
`unit`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`stale`	No
`cached`	No
`source`	No
`adjusted`	No
`disclaimer`	No
`yields_pct`	No	tenor ('1 Mo' ... '30 Yr') -> percent
`cache_seconds`	No
`requested_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint and destructiveHint=false, so safety is covered; the description goes well beyond by disclosing the 6-hour cache, latency range (0.1 s cached vs ~25 s uncached), the adjusted:true fallback behavior, and charged vs non-charged error semantics (422/503). This is unusually rich operational context.

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?

The purpose and routing pointer are front-loaded and the operational facts are packed efficiently, but the trailing boilerplate (pricing, free-tier quota, disclaimer, docs URL) lengthens it beyond what an agent strictly needs to select and call the tool.

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

Completeness5/5

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

With an output schema present, return values need not be explained, and the description still covers the null-when-unpublished and adjusted-fallback semantics. For a single-parameter read tool, an agent has everything needed to call it correctly.

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 description coverage is 100% and the sole 'date' parameter is already fully documented, so the baseline is 3. The description largely restates the schema's date-range and adjusted-fallback semantics rather than adding new syntax or format detail.

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 opens with a specific verb and resource ('Get US Treasury yields: the daily par yield curve for a date') and scopes the data precisely (1 Mo to 30 Yr, official US Treasury source). A similar-sounding sibling, get_macro_snapshot, is explicitly differentiated as the tool for SOFR/FX/oil instead.

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

Usage Guidelines5/5

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

It names the alternative tool and the exact condition that selects it ('For SOFR, FX and oil too use get_macro_snapshot'), and states the default behavior when no date is supplied. An agent can route between the two tools without opening either schema.

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

Deploy Server