Tokyo WBGT MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tokyo_wbgt_forecastC | 東京都のWBGT（暑さ指数）予測値を取得します |
| get_all_tokyo_locationsB | 東京都内の全WBGT観測地点の予測値を一括取得します |
| get_tokyo_realtime_dataC | 東京都の実測WBGT値を取得します（実測地点のみ） |
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 3 tools
Each tool has a clearly distinct purpose: get_all_tokyo_locations retrieves predicted values for all observation points, get_tokyo_realtime_data gets measured values for actual observation points only, and get_tokyo_wbgt_forecast obtains forecast values. There is no overlap or ambiguity between these three functions.
All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (all_tokyo_locations, tokyo_realtime_data, tokyo_wbgt_forecast). The naming is perfectly uniform and predictable throughout the set.
Three tools is well-scoped for a Tokyo WBGT server focused on location data, real-time measurements, and forecasts. Each tool earns its place without redundancy, and the count is appropriate for the apparent domain scope.
The tools cover the core WBGT data retrieval needs (locations, real-time, forecasts) for Tokyo, with no obvious dead ends. A minor gap might be historical data or alerts, but agents can work effectively with the provided surface for typical weather/heat index queries.