Fetch current modeled weather and daily forecasts from Open-Meteo for any latitude and longitude, with an optional 1-7 day outlook.
Retrieve current modeled weather and daily forecasts from Open-Meteo.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| latitude | Yes | ||
| longitude | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that data is 'modeled' and sourced from Open-Meteo, which is useful context, but says nothing about rate limits, auth, units, or timezone handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. Appropriately sized, though the brevity comes at the cost of the missing parameter and usage detail noted above.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With three parameters, no output schema, and annotations covering the safety profile, the description should at minimum hint at the return shape (current conditions plus a daily series) and the coordinate format. It gestures at the return content but leaves the agent guessing on units, location resolution, and response structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the full burden, yet it says nothing about latitude/longitude units or accepted ranges, and 'daily forecasts' only obliquely implies the 'days' parameter (default 3, max 7) without stating it. The agent must read the bare schema to call this correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Retrieve') and resource ('current modeled weather and daily forecasts') plus the data source (Open-Meteo). It is clear enough to distinguish from the task/database siblings, though it never explicitly contrasts with anything.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to call this versus anything else, no prerequisites, no note that a location must be resolved first (e.g. via search_locations). The agent gets context only by inference from the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.