Skip to main content
Glama

Real Yield Rates

rates_real_yield
Read-only

US Treasury real yield (TIPS) series. (Source: US Treasury TIPS.)

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

Input Schema

NameRequiredDescriptionDefault
tenor_codeNoTIPS tenor, e.g. 5y, 7y, 10y.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds essentially nothing beyond source attribution. It does not disclose units (percent vs basis points), observation frequency, default tenor behavior when the optional parameter is omitted, or whether results are a single point or a series over time.

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

Conciseness3/5

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

It is very short and front-loaded, but the parenthetical '(Source: US Treasury TIPS.)' restates 'TIPS' from the first sentence, making the second half largely redundant. Brevity here comes at the cost of substance rather than from efficiency.

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

Completeness2/5

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

For a single-parameter data tool with no output schema, the description should at minimum convey what is returned and how the optional tenor affects it. Neither is present, leaving the agent unable to predict the response shape or the default behavior.

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 single optional tenor_code parameter is well documented with examples in the schema, so the baseline of 3 applies. The description mentions no parameter behavior at all and does not state what happens when tenor_code is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource precisely as the US Treasury real yield (TIPS) series, which distinguishes it from nominal-rate siblings such as rates_treasury_bill. However, it is a bare noun phrase with no verb (fetch/return), so the agent must infer that this is a data-retrieval endpoint rather than, say, a calculator or a description of a series.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives like yield_curve or rates_treasury_bill, nor any condition or exclusion. The agent is left to infer from the name alone that this is the TIPS real-yield variant.

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