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 |
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_weatherA | Get current weather for a city. Args: city: City name (e.g. London, Chennai, New York) Returns: Weather details including temperature, humidity, and conditions. |
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 1 tool
With only one tool, there is no possibility of confusing it with others. The tool's purpose is clearly stated and unambiguous.
The single tool name follows a clear verb_noun pattern. However, with only one example, consistency cannot be fully assessed.
A single tool is too few for a weather-focused server, which would typically also cover forecasts, historical data, or location-based queries. The tool provides only current conditions.
The tool surface is severely limited to current weather only. Obvious gaps include forecasts, severe weather alerts, historical weather, and geocoding or location disambiguation.