Weather-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weather-get_hourlyA | Get hourly weather forecast for the next 12 hours |
| weather-get_dailyA | Get daily weather forecast for up to 15 days |
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 forecast granularity: one provides hourly data for the next 12 hours, the other provides daily data for up to 15 days. There is no meaningful overlap or ambiguity between them.
Both tool names follow the same weather-get_{period} pattern, using the same verb and a consistent naming style. The only differences are the period suffixes, hourly and daily, making the pattern predictable and clear.
Two tools is at the low end and feels thin for a weather server, though the pair does cover the two main forecast modes. The count is borderline rather than clearly insufficient.
The server covers hourly and daily forecasts, but lacks obvious weather-related capabilities such as current conditions, location search, or weather alerts. These are notable gaps that could force agents to work around the limited surface.