Skip to main content
Glama

BondTerminal

US Treasury curve

bondterminal_treasury_curve
Read-onlyIdempotent

Return the current US Treasury curve across 11 standard tenors. Rates and YTM conventions are percent, spreads are basis points, and bond prices are per 100 face. The response is capped at the 11 listed tenors. Billing: free; consumes no calculation or read units.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dateYes
ratesYes
lastUpdatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds value beyond that with unit conventions (percent for rates/YTM, basis points for spreads, price per 100 face), the 11-tenor cap, and the billing note that it consumes no calculation or read units.

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?

Three short sentences with the resource and scope front-loaded, followed by units, cap, and cost. Every sentence carries distinct information and there is no filler.

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

Completeness5/5

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

For a zero-parameter read tool with rich annotations and an output schema, the description supplies everything else an agent needs: units, coverage limit, and cost. Return-value structure is delegated to the output schema, which is appropriate.

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

Parameters4/5

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

The tool takes zero parameters, which sets the baseline at 4. The description's unit conventions describe the response rather than inputs, but they are still useful orientation for interpreting the returned numbers.

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?

States a specific verb and resource — 'Return the current US Treasury curve' — plus the scope of 11 standard tenors. An agent can immediately tell this is a curve snapshot rather than a bond search, calculation, or history call, so no sibling confusion arises.

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: it is a parameterless snapshot read, which an agent can infer, but the description never says when to prefer it over siblings like bondterminal_get_history or bondterminal_calculate. No exclusions or prerequisites are stated.

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