MCP Weather 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherB | Get current weather conditions for a city. Args: city: Name of the city, e.g. "Toronto" or "London, Ontario" |
| get_forecastA | Get a multi-day weather forecast for a city. Args: city: Name of the city, e.g. "Toronto" days: How many days ahead to forecast, 1 to 16. Defaults to 3. |
| get_historicalA | Look up past weather for a city on a specific date. Args: city: Name of the city, e.g. "Toronto" date: The date in YYYY-MM-DD format. Must be at least 5 days in the past. |
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 3 tools
Each tool targets a distinct temporal scope: current, forecast, and historical weather. There is no overlap or ambiguity between them.
All tools follow the same verb_noun pattern (get_ + descriptor) with consistent parameter naming for city, making them predictable.
Three tools cover the core weather server domain—current conditions, forecasts, and historical data—without unnecessary bloat or missing essentials.
The tool surface provides full coverage for typical weather queries: current, future, and past. No obvious gaps exist for a server of this scope.