Skip to main content
Glama

Jgb Yield Curve

jgb_yield_curve
Read-onlyIdempotent

Japan government bond (JGB) yield curve for one day: all 15 benchmark tenors (1Y-10Y, 15Y, 20Y, 25Y, 30Y, 40Y) in percent, from the Ministry of Finance Japan. Omit date for the latest business day. A weekend or holiday returns found:false with the nearest published 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": {
      "date": "2026-11-09"
    },
    "name": "jgb_yield_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date YYYY-MM-DD (business days only). Default: latest.

Output Schema

NameRequiredDescriptionDefault
dateNo
unitNo
foundNo
sourceNo
yieldsNo
data_as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. Beyond that, the description adds real substance the annotations do not: the data source, that values are in percent, full tenor coverage, and the non-obvious edge case that a weekend or holiday yields found:false along with the nearest published days.

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?

Three dense sentences, front-loaded with what the tool returns and followed by the calling convention and the edge case. The parenthetical tenor list is slightly verbose but conveys coverage information an agent could act on; nothing here is filler.

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 single-parameter read tool with an output schema and full annotation coverage, this is nearly complete: source, units, tenor range, default behavior, and holiday handling are all stated. A minor ambiguity remains about whether a holiday response returns only nearest-day metadata or actual curve values, which the output schema presumably resolves.

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?

With 100% schema description coverage and only one optional parameter already documented with a default, the schema does most of the work. The description reinforces the default ('omit date for the latest business day') and clarifies that dates must be business days, but adds no format or syntax detail beyond what the schema states.

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 states a specific verb+resource: the JGB yield curve for one day, with explicit scope (15 benchmark tenors from 1Y to 40Y), units (percent), and provenance (Ministry of Finance Japan). The phrase 'for one day' implicitly separates it from the jgb_yield_history sibling, but it never names that alternative, so the differentiation is inferable rather than 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?

It gives useful calling context: omit the date for the latest business day, and business days only. It also warns about weekend/holiday behavior. What it lacks is explicit routing guidance, e.g. pointing to jgb_yield_history when a range of dates or historical series is wanted, leaving the agent to infer the boundary between the two tools.

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.