MCP Weather Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | Your OpenWeatherMap API key (required for the server) | |
| OPENWEATHER_BASE_URL | No | The base URL for the OpenWeatherMap API | https://api.openweathermap.org/data/2.5 |
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_weatherB | Get the current weather for a city. Args: city: Name of the city (e.g., "Toronto", "London", "Tokyo") Returns: A formatted string with current weather conditions. |
| get_forecastB | Get a multi-day weather forecast for a city. Args: city: Name of the city days: Number of days to forecast (1-5, default 3) Returns: A formatted multi-day forecast summary. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weather_report | Generate a comprehensive weather report for a city. Args: city: Name of the city Returns: A formatted weather report. |
| travel_advisory | Generate a travel weather advisory prompt. Args: city: Destination city days: Trip duration in days |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_supported_cities | List all cities this weather server supports as examples. |
| get_help | Get help on how to use the weather server. |
TDQS
Scored across 2 tools
The two tools have distinct purposes: get_weather for current conditions and get_forecast for multi-day predictions. However, the names could cause minor confusion as 'weather' and 'forecast' are semantically related, but the descriptions clearly differentiate them.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. This makes them predictable and easy to understand at a glance.
With only two tools, the server feels under-scoped for a weather domain. It lacks operations like historical data, alerts, or location-based searches, which are common in weather APIs and would enhance agent capabilities.
The toolset is severely incomplete for a weather server. It covers current and forecast data but misses essential operations like historical weather, severe alerts, air quality, or multi-location queries, leaving significant gaps for agent workflows.