Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | Your OpenWeather API key (get one at https://openweathermap.org/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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherA | Get current weather information for a specific city |
| get_weather_forecastA | Get 5-day weather forecast for a specific city |
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 2 tools
Tools have clearly distinct purposes: one retrieves current weather, the other provides a forecast. No overlap in functionality.
Both tools follow a consistent verb_noun pattern using snake_case: get_current_weather and get_weather_forecast. The pattern is predictable.
With only 2 tools, the set is minimal but borderline for a weather server. A few more (e.g., hourly forecast, alerts) would be more appropriate.
The tool surface covers current weather and a 5-day forecast, but misses common weather operations like hourly forecasts, weather alerts, or location-based queries.