weather-mcp-pro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | Your OpenWeather API key |
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_current_weatherA | Get current weather conditions for a location. Args: location: City name, optionally "City,CountryCode" e.g. "Lahore,PK" units: "metric" (Celsius), "imperial" (Fahrenheit), or "standard" (Kelvin) |
| get_weather_forecastA | Get a multi-day weather forecast for a location. Args: location: City name, optionally "City,CountryCode" days: Number of days to forecast (1-5) units: "metric", "imperial", or "standard" |
| get_air_qualityA | Get current air quality index (AQI) and pollutant breakdown for a location. Args: location: City name, optionally "City,CountryCode" |
| compare_weatherA | Compare current weather across multiple locations side by side. Args: locations: List of city names, e.g. ["Peshawar", "Lahore", "Islamabad"] units: "metric", "imperial", or "standard" |
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 4 tools
Each tool targets a distinct weather data aspect: current conditions, multi-day forecast, air quality, and multi-location comparison. There is no overlap in purpose, so an agent can easily select the right tool.
Three tools follow the `get_<noun>` pattern (get_current_weather, get_weather_forecast, get_air_quality), but `compare_weather` deviates by using a different verb. The pattern is mostly consistent and readable.
With 4 tools, the server is well-scoped for a weather domain. Each tool earns its place, covering the essential weather queries without unnecessary bloat.
The surface covers current weather, forecasts, air quality, and comparisons, which addresses typical use cases. Minor gaps exist such as no historical weather or weather alerts, but these are not critical for basic weather retrieval.