Weather MCP Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | Your OpenWeatherMap 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 |
|---|---|
| fetch_current_weatherA | Fetch the current weather conditions for a given city. Args: city (str): Name of the city to fetch weather data for. Returns: dict[str, Any]: A dictionary containing the city, country, temperature, feels-like temperature, min/max temperature, humidity, and weather description. Returns a dictionary with an "error" key if the request fails or the data cannot be retrieved. |
| fetch_weather_forecastA | Fetch the weather forecast for a given city. Args: city (str): Name of the city to fetch forecast data for. Returns: dict[str, Any]: A dictionary containing the city, country, and a list of forecast entries (temperature, datetime, and description) at 3-hour intervals. Returns a dictionary with an "error" key if the request fails or the data cannot be retrieved. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| weather_config_resource |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one provides current conditions, the other provides a forecast. There is no overlap or ambiguity between them.
Both tool names follow a consistent 'fetch_' + noun pattern, with names fetch_current_weather and fetch_weather_forecast. The naming is predictable and uniform.
With only 2 tools, the set is on the thin side for a weather server, though it covers the core current and forecast needs. It feels slightly minimal but not inadequate.
The server covers the two most essential weather operations: current conditions and forecasts. Notable gaps include historical weather data and alerts, but these are optional extras rather than essential missing functionality.