Retrieves daily weather forecasts for 1–7 days for any location, with configurable units. Use it to check upcoming conditions and plan activities.
Get a daily weather forecast for 1–7 days for a location.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| unit | No | celsius | |
| location | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full disclosure burden; it only adds the 1–7 day constraint and 'Get' implies a read operation. It does not state whether calls are read-only, what happens outside the range, location format expectations, or any service/auth limits, leaving meaningful behavioral gaps.
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?
The description is a single front-loaded sentence with no filler, and it efficiently states the operation, horizon, and target. There is no structural ambiguity or unnecessary wording.
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?
An output schema exists, so return values need not be described. However, with no annotations and no parameter descriptions in the schema, the definition leaves unit semantics, range enforcement, and sibling differentiation unexplained, which is sparse for correct tool selection and use.
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 must explain the three parameters itself. It gives a range for days and mentions location, but never addresses the unit parameter, valid unit values, or location formatting, so it only partially compensates.
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?
The description names a specific verb and resource: 'Get a daily weather forecast' with a 1–7 day scope and a required location, so the operation is understandable. It does not distinguish this from the sibling get_weather or explain how forecast differs from weather, so it is not a 5.
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?
The description gives no explicit when-to-use guidance and does not mention get_weather as the alternative for current conditions. The 1–7 day wording implies a forecast horizon, but it does not say when this tool should be selected over the sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.