wetter-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_LAT | No | Latitude for default location (optional) | |
| DEFAULT_LON | No | Longitude for default location (optional) | |
| DEFAULT_ORT | No | Name of default location (optional) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherB | Aktuelles Wetter: Temperatur, gefühlte Temperatur, Luftfeuchte, Wind, Bewölkung, aktueller Niederschlag. Ohne location = Zuhause (Steinenbronn). |
| get_hourly_forecastA | Stündliche Vorhersage: Temperatur, Regen (mm + Wahrscheinlichkeit), Wind, Wetterlage. hours 1–48 (Standard 24). Ohne location = Zuhause. Für 'kann ich die Fenster nachts offen lassen?' die Nachtstunden auf Niederschlag und Minimaltemperatur prüfen. |
| get_daily_forecastA | Tagesvorhersage: Min/Max-Temperatur, Regensumme + Wahrscheinlichkeit, Sonnenstunden, Wetterlage. days 1–16 (Standard 7). Ohne location = Zuhause. Für Reisewetter je Roadtrip-Station die location auf den jeweiligen Ort setzen. |
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 has a clearly distinct purpose: current conditions, daily forecast, and hourly forecast. There's no overlap or ambiguity between them.
All tools follow the same get_*_forecast pattern (with get_current_weather as the one slight variation, but still consistent verb_noun structure). Naming is clear and predictable.
Three tools is an appropriate scope for a weather server, covering current, daily, and hourly data without unnecessary overlap.
The set covers the most common weather queries (current, daily, hourly). Missing advanced features like alerts or historical data, but the core is well-covered for typical use.