Weather MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENWEATHER_API_KEY | Yes | API key for OpenWeatherMap |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getWeatherB | Get the weather for a city |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| getWeather | Fetch weather for a city |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined by its name and description.
The single tool uses a consistent verb_noun pattern (get_weather). There are no other tools to introduce inconsistency.
One tool is on the low end but can be acceptable for a very narrow scope. However, a weather server typically warrants more than a single tool, so the count feels thin.
The tool only supports current weather for a city, but a complete weather domain would also include forecasts, historical data, or alerts. These missing operations represent significant gaps that would force agents to rely on external workarounds.