boj-jstat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| boj_list_databasesA | List all available BOJ statistical databases. Use this first to find the correct DB code before querying data. No API call needed — uses a static list of 40+ databases. |
| boj_get_metadataA | Get metadata (series codes, names, units, frequencies, layer structure) for a BOJ database. Use this to discover available series codes and understand the database structure before fetching actual data. NOTE: Large databases like CO (Tankan, 168k series) require a small limit (e.g. 20-50) to avoid overwhelming responses — use layer-based queries to navigate them. |
| boj_get_data_codeA | Fetch time series data by SERIES_CODE(s). All specified codes must share the same frequency. Returns up to 250 series / 60,000 data points per request. If a code is invalid, the server tries metadata-assisted correction for close matches and returns concrete suggestions. |
| boj_get_data_layerA | Fetch time series data by layer (hierarchical structure). Useful for browsing data by category within a database. Supports wildcard '*'. Returns up to 1,250 series / 60,000 data points per request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing databases, fetching data by code, fetching data by layer, and retrieving metadata. There is no overlap or ambiguity.
All tools follow a consistent 'boj_verb_object' pattern (e.g., boj_list_databases, boj_get_data_code), making it easy for agents to predict function.
Four tools is well-scoped for a statistical data server, covering essential operations without redundancy or bloat.
The tool set covers the full workflow: discover databases, explore metadata, and retrieve data via two complementary methods (by code and by layer). No obvious gaps.