Skip to main content
Glama

Boj Series

boj_series
Read-onlyIdempotent

Any Bank of Japan statistics time series by database id and series code: money stock and monetary base, TANKAN, corporate goods price index, flow of funds, loans and deposits, balance of payments. Returns name, unit, frequency, last update date, observations and a computed YoY percentage for monthly, quarterly and annual series. A period the BOJ has not published yet returns reason not_yet_published with the latest available value. Find codes with boj_series_list.

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": {
      "db": "MD02",
      "code": "MAM1NAM2M2MO",
      "start": "2026-07"
    },
    "name": "boj_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbYesBOJ database id, e.g. 'MD02' (money stock), 'MD01' (monetary base).
endNoLast period, same format.
codeYesSeries code, e.g. 'MAM1NAM2M2MO' (M2 average amounts outstanding).
limitNoMax observations returned (default 24, max 240).
startNoFirst period: '2026-01', '2026Q1' or '2026' depending on frequency.

Output Schema

NameRequiredDescriptionDefault
dbNoBOJ database id
codeNoSeries code
hintNoNext step
nameNoSeries name
unitNoUnit as published
foundNoWhether data was found
notesNo
latestNoOne observation
reasonNonot_yet_published, series_not_found, no_observations, no_observations_in_range, database_not_found, no_matching_series, database_too_large_to_list
sourceNoPublisher and dataset
measureNoMoney stock measure label
messageNoExplanation when found is false
categoryNoSeries category
frequencyNomonthly, quarterly or annual
requestedNoRequested period (not_yet_published)
data_as_ofNoNewest period in the series
last_updateNoDate the BOJ last updated the series (YYYYMMDD)
observationsNo
series_rangeNoFirst and last period
observation_countNoObservations returned
latest_available_valueNoNewest published value (not_yet_published)
latest_available_periodNoNewest published period (not_yet_published)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it returns name, unit, frequency, last update date, observations and a computed YoY for monthly, quarterly and annual series, and it specifies that an unpublished period returns reason not_yet_published with the latest available value. That is solid added context, but the return-field list overlaps with the existing output schema.

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 front-loaded sentences: capability, then return/edge-case semantics, then the code-discovery pointer. The domain enumeration is long but earns its place by signaling breadth; little is wasted.

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 five-parameter, two-required read tool with full schema coverage, annotations and an output schema, the description covers purpose, the not_yet_published edge case, and how to obtain a valid series code. Nothing an agent needs in order to call it correctly 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 description coverage is 100% and the schema already carries per-parameter descriptions plus working examples for db, code, start, end and limit. The description only reinforces the db/code pairing and the period format, adding little meaning beyond the schema, so baseline 3 applies.

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 gives a specific verb and resource ('Any Bank of Japan statistics time series by database id and series code') and enumerates the covered domains (money stock, TANKAN, CGPI, flow of funds, loans/deposits, balance of payments), so an agent can immediately tell what this tool fetches versus the narrower siblings like boj_money_stock or boj_inflation.

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 closes with an explicit routing instruction: 'Find codes with boj_series_list,' which tells the agent the prerequisite discovery step. It stops short of distinguishing when to prefer the specialized siblings (boj_inflation, boj_policy_rate, boj_money_stock) over this generic fetcher, so there is clear context but no exclusions.

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.