Skip to main content
Glama
Sign In

Treasury Yields and Rates Today MCP

by io.github.theluckystrike
OverviewDiscussionsAdmin

Treasury yield history

treasury_yield_history
Read-onlyIdempotent

History of one Treasury yield (e.g. 10y, 2y, 3m, 30y) between two dates: start, end, change, high, low and average, with a daily or sampled table. Up to 731 days per call, back to 1990.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenor": "<tenor>"
    },
    "name": "treasury_yield_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD. Default today.
startNoYYYY-MM-DD. Default 30 days before end.
tenorYesMaturity: 1m, 1.5m, 2m, 3m, 4m, 6m, 1y, 2y, 3y, 5y, 7y, 10y, 20y or 30y.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds genuinely new behavioral facts: a hard 731-day-per-call window and coverage back to 1990, both of which shape how the agent batches requests.

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

Conciseness5/5

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

A single sentence front-loads the resource and scope, then packs the return fields and the two hard limits into a compact clause. Nothing is redundant or buried.

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 usefully enumerates the returned fields (start, end, change, high, low, average) and notes a daily or sampled table. The unexplained 'sampled' mode, which no parameter controls, is the one loose end for a three-parameter read tool.

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%, so tenor enumeration, date patterns, and the today/30-days-before defaults are already fully documented. The description's tenor examples and 'between two dates' phrasing restate the schema rather than adding format or edge-case meaning, so the baseline 3 applies.

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 states a specific verb and resource: the history of one Treasury yield over a date range, with named tenors (10y, 2y, 3m, 30y). The emphasis on 'one' tenor implicitly separates it from treasury_yield_curve, which implies multiple maturities, but it never names that sibling explicitly.

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 by the framing (single tenor, date-bounded history) and the constraints (731 days per call, back to 1990) tell the agent when the call will fail or needs splitting. There is no explicit when-to-use statement or named alternative for multi-tenor or curve queries.

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

All Treasury Yields and Rates Today MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources