Weather MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherA | Get current weather for a given 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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and distinct by default.
The tool name follows a consistent verb_noun pattern (get_weather). With a single tool, there are no naming inconsistencies to evaluate.
One tool feels thin for a weather server, which typically offers multiple data types like forecasts and alerts. However, it is borderline given the narrow 'current weather' scope.
The server only covers current conditions, missing obvious weather domain features such as forecasts, historical data, or alerts. This significantly limits its usefulness for common weather queries.