Skip to main content
Glama

BankRegReports

Treasury Yield Curve

yield_curve
Read-only

US Treasury yield curve (long form). Pass ?latest=1 for the current curve. (Source: US Treasury.)

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

Input Schema

NameRequiredDescriptionDefault
latestNoReturn only the current curve.
tenor_codeNoOne tenor series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds provenance (US Treasury) and the long-form vs current-curve distinction, but says nothing about coverage of historical dates, refresh cadence, or response shape.

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?

Three short sentences, front-loaded with what the tool returns, with zero filler. The unexplained term 'long form' is the one place where brevity costs clarity.

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 two-parameter read-only data fetch with no output schema, the description should say what the default call returns (e.g., all tenors, what date range) and what 'long form' means. It covers source and the latest flag but leaves the default return ambiguous.

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 both parameters are already documented, and the description's '?latest=1' note largely restates the schema's example value of '1'. The URL-style '?latest=1' phrasing is also slightly misleading for a tool argument rather than a query string, though it is consistent with the schema.

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 a specific resource — the US Treasury yield curve in long form — with a clear source attribution, so an agent knows exactly what data it retrieves. It does not differentiate itself from plausible siblings such as rates_real_yield or rates_treasury_bill, leaving that distinction to inference.

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?

The only conditional guidance is 'Pass ?latest=1 for the current curve,' which explains how to switch between the long-form series and the current snapshot. There is no statement of when to prefer this tool over the sibling rate tools, nor any exclusion or prerequisite.

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.

Resources