korea_weather
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KOREA_WEATHER_API_KEY | Yes | API key for Korea Weather MCP server, obtained from data.go.kr |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nowcast_observationB | 특정 좌표의 현재 관측 날씨를 조회합니다. |
| get_nowcast_forecastA | 특정 좌표의 초단기(6시간) 예보를 조회합니다. |
| get_short_term_forecastB | 특정 좌표의 단기(3~5일) 예보를 조회합니다. |
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 targets a distinct temporal scope: current observation, 6-hour nowcast, and 3-5 day forecast. No overlap in purpose.
All tool names follow the get_ prefix with descriptive qualifiers and nouns, using snake_case consistently. The naming pattern is uniform and predictable.
With only 3 tools, the server is tightly scoped to its purpose of providing weather data. Each tool covers a necessary aspect, and the count falls within the ideal 3-15 range.
The core weather data needs are covered: current conditions, short-term nowcast, and multi-day forecast. Minor gaps like long-range forecasts or alerts exist, but the primary use case is well-served.