Skip to main content
Glama

BondTerminal

Bond history

bondterminal_get_history
Read-onlyIdempotent

Return daily price, YTM, YTW, and spread history for one bond using a named range or explicit dates. YTM is percent, semi-annual bond-equivalent (S.A.) for every bond; spreads are basis points on the same basis, except EUR bonds, whose spreads are over the Bund curve on the annual basis (spreads.benchmark BUND, yields.ytmAnnual); and prices are per 100 face. Yield conventions: https://bondterminal.com/methodology/yields Explicit ranges are capped at 730 days and responses at 750 points. Billing: 10 read units per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "bondterminal_get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLast day, YYYY-MM-DD. Needs start; at most 730 days after it.
rangeNoNamed window: 1w, 1m, 3m, ytd, 1y or 2y. start and end replace it when both are given.1m
startNoFirst day, YYYY-MM-DD. Needs end.
identifierYesOne bond: ISIN, CUSIP, ticker or Argentine local ticker (for example AL30 or GD30).

Output Schema

NameRequiredDescriptionDefault
urlNoThe bond page on bondterminal.com.
isinYes
rangeYes
seriesYes
tickerNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / end / description
      Added value: +"Last day, YYYY-MM-DD. Needs start; at most 730 days after it."
    • addedInput schema / properties / identifier / description
      Added value: +"One bond: ISIN, CUSIP, ticker or Argentine local ticker (for example AL30 or GD30)."
    • addedInput schema / properties / range / description
      Added value: +"Named window: 1w, 1m, 3m, ytd, 1y or 2y. start and end replace it when both are given."
    • addedInput schema / properties / start / description
      Added value: +"First day, YYYY-MM-DD. Needs end."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes well beyond that with hard limits (explicit ranges capped at 730 days, responses at 750 points) and billing cost ('10 read units per call'), both of which an agent needs before deciding to call.

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

Conciseness4/5

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

Front-loaded with the core purpose and the range-or-dates mechanism, then limits and billing. The unit-convention sentence is long and dense with nested parentheticals, but every clause carries semantic content (percent S.A., bps, EUR Bund exception, per-100 face).

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?

An output schema exists, so return structure need not be described, yet the description usefully adds the units and basis conventions that the schema would not convey. Combined with explicit caps, billing and a methodology link, an agent has everything needed to call this correctly for a 4-parameter read tool.

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 coverage is 100%, so the baseline is 3; the schema already documents range enumerations, date patterns and the start/end dependency. The description's added detail (units and bases for the returned values, the EUR/Bund exception) enriches interpretation of the output rather than the input parameters, so it does not raise this above baseline.

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 daily price, YTM, YTW, and spread history') scoped to 'one bond', and enumerates the exact data fields returned. The 'one bond' scope combined with the identifier parameter clearly separates it from the sibling search/list tools.

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?

The description notes the two modes of invocation ('a named range or explicit dates') and the schema states that start/end replace range, so the mechanics of choosing are covered. However, it gives no guidance on when to use this tool versus siblings like bondterminal_get_bonds or bondterminal_search_bonds, and 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