Skip to main content
Glama
jp-statistics-mcp

jp-statistics-mcp

by koizumikento

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_indicatorsB

Find indicator codes by Japanese or English text in the indicator name.

get_indicator_dataC

Get series data. Cycles: 1 month, 2 quarter, 3 calendar year, 4 fiscal year.

search_regionsA

Find region codes by name, kana reading or code. Omit query to browse.

search_termsB

Find statistical terms by name or code and read definitions and reference links.

search_social_eventsC

Find social events by name or code, with their periods and statistical categories.

search_surveysA

Find statistical surveys by name or code, with agency, summary and reference link.

search_seriesB

Find series by Japanese name, English name or code within a BOJ database.

get_series_dataB

Fetch observations for one BOJ series. Periods are YYYY or YYYYMM by frequency.

get_multiple_series_dataB

Fetch up to 250 codes from one DB and one frequency. Resume from NEXTPOSITION.

get_series_data_by_layerC

Fetch observations by comma-separated layer path (e.g. '1,2,*'). Resume from NEXTPOSITION.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 10 tools

Disambiguation3/5

The six search_* tools are cleanly separated by entity (indicator, region, term, social event, survey, series), but the data-fetch tools overlap: get_series_data, get_multiple_series_data, get_series_data_by_layer and get_indicator_data all sound like 'get time series data' and only the descriptions reveal that two are BOJ-series based and two are e-Stat layer/indicator based. The shared word 'series' across both e-Stat and BOJ tools invites misselection.

Naming Consistency4/5

All tools are snake_case with a verb_noun shape (search_*, get_*_data), so the pattern is predictable. Minor deviations: get_series_data_by_layer and get_multiple_series_data are longer qualified variants, and get_indicator_data lacks the 'series/indicator' symmetry with its siblings.

Tool Count4/5

Ten tools is a well-scoped count for a server spanning two data sources (e-Stat catalog entities plus BOJ series). Each tool maps to a distinct entity or fetch mode, with no obviously redundant entries.

Completeness3/5

There is search coverage for indicators, regions, terms, events, surveys and BOJ series plus data retrieval, but gaps remain: no tool to enumerate available databases/layers (the layer path required by get_series_data_by_layer and the 'one DB' required by get_multiple_series_data must come from outside the toolset), and no metadata/definition lookup for a BOJ series beyond the name search. Pagination via NEXTPOSITION is handled for only two of the fetch tools.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues