Skip to main content
Glama

get_yield_curve_benchmark

Read-only

Live US Treasury yield curve — 1M through 30Y yields with daily and weekly basis point changes, 2s10s and 2s30s spreads, inversion signal, SOFR, and curve shape classification. Source: FRED. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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_yield_curve_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint), and the description adds real behavior beyond them: a $0.10 USDC x402 charge per call, a no-charge HTTP 503 on upstream failure, and a data_source field disclosing fred_api/fred_csv/fred_mixed provenance. Those are exactly the cost and failure semantics an agent cannot get from annotations. It does not describe response shape or latency, keeping it at 4.

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?

The field enumeration is front-loaded and dense with useful content, but the 503/no-charge clause is stated twice in near-identical wording, and 'Source: FRED. Live source.' splits one idea across two fragments. Redundancy and the pipe-delimited pricing block cost it clarity.

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 does the work of describing returns by naming the fields the caller receives, plus pricing, failure behavior and provenance. The remaining gap is the tenor parameter, which is left entirely unexplained despite being the only input. For a single-purpose data-fetch tool this is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'tenor' parameter has 0% schema description coverage and the description never mentions it, so nothing explains what '2y'/'10y'/'30y' scope the response to or what 'all' yields by default. The '1M through 30Y' phrasing hints the default is the full curve, but that is inference, not stated meaning. With the schema carrying no descriptions, the description should have compensated and does not.

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 (US Treasury yield curve) and enumerates exactly what comes back: 1M–30Y yields, daily/weekly bp changes, 2s10s and 2s30s spreads, inversion signal, SOFR, curve shape. That is far more specific than a tautology and separates it from the corporate-debt, credit-spread and FX siblings. It stops short of an explicit 'this is the risk-free benchmark, not X' contrast, so a 4 rather than 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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. Usage is only implied by the field list — an agent can infer this is for risk-free Treasury curve data, but must derive that itself. Implied-only guidance fits a 3.

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