Skip to main content
Glama

Boj Money Stock

boj_money_stock
Read-onlyIdempotent

Japan's money stock (M1, M2, M3, or L) from the Bank of Japan, monthly, average amounts outstanding, in 100 million yen, with a computed year-over-year growth rate for every observation. Use for 'Japan M2 money supply growth' / 'Japan M3 YoY' / 'BOJ money stock for a month'. Pass month (e.g. '2026-10') to get one month; a month the BOJ has not published yet returns reason not_yet_published together with the latest available value instead of an empty result.

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": {
      "month": "2026-09",
      "measure": "M2"
    },
    "name": "boj_money_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLast month of a range.
limitNoMax observations returned (default 24, max 240).
monthNoOne month, e.g. '2026-10' or '202610'.
startNoFirst month of a range, e.g. '2026-01'.
measureNoWhich aggregate (default M2).
seasonally_adjustedNoUse the seasonally adjusted series (default false, the headline unadjusted series).

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.7/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 the description adds genuinely new behavior: the unit of measurement, the computed YoY per observation, and the non-obvious edge case that an unpublished month returns reason=not_yet_published plus the latest available value rather than an empty result. That unpublished-month fallback is exactly the kind of surprise an agent needs to know before calling.

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?

Two sentences, front-loaded with what the data is and how it is measured, followed by concrete query triggers and the edge-case behavior. Every clause carries information; nothing is restated from the title.

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?

With six optional parameters fully documented in the schema and an output schema present, the description only needs to cover scope, units, and edge-case behavior — all of which it does. Nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: 'month' is framed as fetching a single month versus the range semantics of start/end, and it explains the special outcome for a future month. It does not mention the seasonally_adjusted toggle (left entirely to the schema), so it is not a full 5.

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 resource (Japan's money stock from the Bank of Japan), the exact enumerable measures (M1, M2, M3, L), the frequency, the unit (100 million yen), and the derived field (computed YoY growth). An agent can distinguish this from boj_inflation, boj_policy_rate, and boj_series purely from the text.

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?

Gives concrete trigger phrasings ('Japan M2 money supply growth', 'Japan M3 YoY', 'BOJ money stock for a month') and explains the single-month mode versus the range mode implied by start/end. It does not explicitly name when to prefer a sibling tool or exclude a use case, so it stops short of a 5.

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.