Skip to main content
Glama

Ellimist

U.S. Treasury par yield curve

data_macro_treasury_curve
Read-only

Use this to get the U.S. Treasury par yield curve (1-month to 30-year yields) by day, with 10y-2y and 10y-3m spreads for recession and rates signals. Official data. Price: $0.005 USDC per call via x402 (no account). Not charged if it fails.

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

Input Schema

NameRequiredDescriptionDefault
endNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful non-schema behavior: a $0.005 USDC x402 charge per call, no account requirement, and no charge on failure, though it does not cover data freshness or rate limits.

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?

The description is three efficient sentences, front-loading the core purpose and data coverage, then adding official-data and pricing context. Every sentence adds relevant information without waste.

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 macro data tool with no output schema, the description covers purpose, data granularity, spreads, and payment behavior well. Its main gap is insufficient explanation of the optional date parameters and their defaults.

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?

Schema description coverage is 0%, and the description does not explain the optional start/end parameters, their date format, defaults, or whether the range is inclusive. 'By day' weakly implies a date range but does not compensate for the undocumented parameters.

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

Purpose5/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: get the U.S. Treasury par yield curve, including 1-month to 30-year yields by day and 10y-2y/10y-3m spreads. This clearly distinguishes it from sibling macro and DeFi yield tools.

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

Usage Guidelines4/5

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

It gives clear intended usage for recession and rates signals and notes that the data is official. It does not explicitly compare against alternatives such as data_macro_recession_signals or data_defi_yield_vs_tbill, so exclusion guidance is missing.

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