weather-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport (default: 3000). | |
| MCP_API_KEYS | No | Comma-separated list of API keys for HTTP transport. If unset, a dev-local-key is generated. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocode_locationA | Resolve a free-text place name (e.g. "Tokyo", "Springfield, Illinois") to candidate latitude/longitude coordinates. Use this first when a user names an ambiguous place, then pass the chosen coordinates to the weather tools. |
| get_current_weatherA | Get current weather conditions for a location. Specify EITHER a "city" name (it will be geocoded automatically) OR explicit "latitude" and "longitude". Returns temperature, "feels like", humidity, precipitation, wind, and a human-readable condition. |
| get_forecastA | Get a daily weather forecast (1-16 days) for a location. Specify EITHER a "city" name OR "latitude"+"longitude". Returns per-day high/low temperatures, precipitation total and probability, peak wind, and condition. |
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 operation: geocoding text to coordinates, current conditions, and multi-day forecast. The two weather tools are cleanly separated by time horizon, and the geocode tool's role (disambiguating place names) is explicitly stated, so an agent can pick correctly.
All three names follow a snake_case verb_noun pattern (geocode_location, get_current_weather, get_forecast) with clear, domain-appropriate verbs. No mixed conventions or vague verbs.
Three tools is on the lean side, but each earns its place: geocoding, current conditions, and forecast form a minimal coherent surface. Nothing extraneous, though the surface is small enough that it borders on thin.
Core weather workflows are covered: location resolution, current conditions, and forecasts up to 16 days with temperature, precipitation, and wind. Minor gaps remain, such as hourly forecasts, historical data, or severe-weather alerts, which agents cannot work around without another server.