open-meteo-mcp
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_forecastA | Look up the daily weather forecast for a city, for anywhere from 1 to 7 days ahead. Use this when the question is about the future — what tomorrow looks like, whether the weekend will be dry, whether to pack for rain. You get one entry per day with the expected conditions, high and low temperature, chance and amount of rain, and peak wind speed. For conditions at this exact moment, use get_current instead. |
| get_currentA | Find out what the weather is like in a city right now. Use this for questions about the present moment — whether it is raining, how warm it is, whether someone needs a jacket before heading out. You get the conditions, temperature and what it feels like, humidity, wind, and recent precipitation, measured at the city's local time. If you need tomorrow or the days after, use get_forecast instead. |
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 2 tools
The two tools are clearly separated by time: get_forecast for future days and get_current for the present moment. Each description explicitly references the other to prevent confusion.
Both tool names follow the exact same verb_noun pattern: get_ + forecast/current. This is perfectly consistent and predictable.
With only 2 tools, the server feels thin but not unusable. For a focused weather-with-current-and-forecast scope, it is borderline acceptable, though a richer API would typically include more.
The two tools cover the primary current and short-term forecast use cases. Missing historical data and weather alerts are notable gaps, but for many queries these tools are sufficient.