Skip to main content
Glama

FinanceQuery

Treasury Yield Curve

get_treasury_yields
Read-onlyIdempotent

Get US Treasury yield curve data (1m through 30y) for a given year. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear to fetch yield curve data for (default: current year)
limitNoMaximum rows per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the description needn't restate safety. It does add one useful operational fact — 'No API key required' — but says nothing about pagination semantics (despite limit/cursor params), rate limits, or freshness of the data.

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?

Two short sentences, front-loaded with the resource and scope, with zero redundant or filler wording.

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?

For a simple read-only data tool with rich annotations, a fully documented schema, and no output schema, this is nearly sufficient. The remaining gap is behavioral: it never mentions that results are paginated, even though cursor and limit parameters exist.

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 all four parameters (year, limit, cursor, fields) are already documented, which sets the baseline at 3. The description's 'for a given year' merely echoes the schema's year parameter and adds no format or default detail beyond it.

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 gives a specific verb and resource ('Get US Treasury yield curve data') plus scope details (1m through 30y maturities, per-year granularity), which clearly separates it from siblings like get_treasury_auctions or get_fred_series. It does not explicitly name or contrast an alternative, so it stops short of a 5.

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 only implied: fetch the curve for a year. There is no statement of when to prefer this over get_fred_series or get_treasury_auctions, no exclusions, and no prerequisite guidance beyond the auth note.

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.