Skip to main content
Glama
woongaro

KMA Weather MCP Server

by woongaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KMA_API_KEY_DECODEDYesGeneral authentication key (Decoding) for the Korea Meteorological Administration (KMA) Short-term Forecast Open API.

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_ultra_short_term_forecastB
Get Ultra Short Term Forecast (Next 6 hours).
useful for: checking immediate weather changes, near-future rain/snow probability.
get_village_forecastB
Get Village Forecast (Short Term, up to 3 days).
useful for: planning for tomorrow or the day after, checking daily highs/lows.
Note: Can be slow as it returns a lot of data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_seoul_weather_nowGet current weather for Seoul (Grid: 60, 127).
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one provides an ultra short-term forecast for the next 6 hours, while the other offers a village forecast for up to 3 days. There is no overlap in their temporal scope or use cases, making it easy for an agent to choose the appropriate tool based on the required timeframe.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive names (get_ultra_short_term_forecast and get_village_forecast). The naming is predictable and readable, adhering to snake_case throughout without any deviations.

Tool Count2/5

With only 2 tools, the server feels thin for a weather forecasting domain, as it lacks coverage for common needs like current conditions, alerts, or longer-term forecasts beyond 3 days. This limited scope may hinder agents from performing comprehensive weather-related tasks.

Completeness2/5

The toolset is severely incomplete for weather forecasting, missing essential operations such as getting current weather, historical data, or severe weather alerts. While the two tools cover short-term forecasts, the absence of broader functionality creates significant gaps that could lead to agent failures in real-world scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources