JMA Data 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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_station_infoA | Get AMeDAS station information by station code. |
| search_stationsA | Search AMeDAS stations by name (Japanese, Kana, or English). |
| search_nearby_stationsC | Search AMeDAS stations within a radius from given coordinates. |
| get_stations_of_typeC | Get all AMeDAS stations of a specific type. |
| list_stationsA | List all AMeDAS stations (1286 stations) with pagination. |
| get_current_weatherA | Get current weather observation data from AMeDAS stations. |
| get_weather_by_locationA | Get current weather from the nearest AMeDAS station to given coordinates. |
| get_forecastB | Get weather forecast for a prefecture. |
| list_prefecturesA | List all available prefecture codes for weather forecast. |
| get_historical_weatherA | Get historical weather data for a specific date and time. Data is available for approximately the past 1-2 weeks. |
| get_weather_time_seriesA | Get time series weather data for a station. Useful for analyzing weather trends over hours or days. |
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 11 tools
Station lookup tools are split by clear query mode (code, name, coordinates, type, list-all), and weather tools are separated by temporal scope and access pattern (current, location-based, forecast, historical, time series). No two tools appear to do the same thing.
All names use snake_case with a predictable verb_noun structure (get_, search_, list_), including compound names like search_nearby_stations and get_weather_by_location. The convention is consistent throughout.
11 tools is well-scoped for a station-and-weather data server. Each tool covers a distinct retrieval mode without excessive granularity.
The surface covers station discovery thoroughly and weather retrieval across current, forecast, historical, and time-series modes. Minor gaps exist, such as forecast retrieval by coordinates rather than only prefecture, but core workflows are supported.