Skip to main content
Glama

Jgb Yield History

jgb_yield_history
Read-onlyIdempotent

History of one JGB yield tenor (e.g. 10Y, 30Y) over a date range, oldest first, in percent, from the Ministry of Finance Japan. Daily back to 1974 (long tenors from their first issuance). Default range: the last 90 days.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "2026-11-09",
      "from": "2026-10-01",
      "tenor": "30Y"
    },
    "name": "jgb_yield_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO end date YYYY-MM-DD. Default: latest.
fromNoISO start date YYYY-MM-DD. Default: 90 days before the end.
limitNoMax rows (default 500, max 2000); the most recent rows are kept.
tenorYesOne of 1Y,2Y,3Y,4Y,5Y,6Y,7Y,8Y,9Y,10Y,15Y,20Y,25Y,30Y,40Y (case-insensitive; "10" works).

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
rowsNo
unitNo
countNo
foundNo
tenorNo
sourceNo
truncatedNo
data_as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds substantive context beyond them: data source (Ministry of Finance Japan), units in percent, oldest-first ordering, historical depth to 1974, and the default range.

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 compact sentences, each carrying distinct information (scope, source/units/ordering/depth, default range) with no redundant wording; the core scope is front-loaded.

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?

An output schema exists and annotations are rich, so return values and safety need not be spelled out. Source, units, ordering, coverage window, and defaults are all present; only explicit alternative-tool routing is missing.

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 tenor/from/to/limit are already fully documented, including the limit row cap and the tenor enumeration. The description only reinforces the default window and output ordering, which is baseline-level added value.

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?

States a specific resource and scope: "History of one JGB yield tenor (e.g. 10Y, 30Y) over a date range." The "one tenor" phrasing implicitly contrasts with the curve sibling without naming it, so differentiation is inferable but not explicit.

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 implied rather than stated: the temporal-depth note ("Daily back to 1974") and the default 90-day window tell an agent this is the single-series time-series lookup, but there is no explicit when-to-use versus jgb_yield_curve guidance.

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.