WindWise MCP

Current weather and hourly forecast

get_weather

Read-onlyIdempotent

Retrieves current conditions and an hourly forecast (temperature, rain, cloud, wind) for a place to answer general weather questions, with local times and wind in knots.

Instructions

Current conditions plus an hourly forecast (temperature, rain, cloud, wind) for a place. Use for general 'what's the weather' questions. Wind is in knots, times are local to the location. For wind-sport planning prefer get_wind_forecast or find_wind_windows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_weather"
  }
}

Input Schema

Name	Required	Description
`hours`	No	How many hours ahead to return, starting from the current hour (1-168).
`latitude`	No	Latitude in decimal degrees.
`location`	No	Place name, optionally with region/country to disambiguate, e.g. "Bucerias, Mexico" or "Springfield, US". Ignored for lookup when latitude and longitude are given (then only a label).
`longitude`	No	Longitude in decimal degrees.

Output Schema

Name	Required	Description
`units`	Yes
`caveat`	Yes
`hourly`	Yes
`current`	Yes
`location`	Yes
`attribution`	Yes	Required credit for the data source.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnly, idempotent and open-world behavior, so the bar is lower. The description adds genuinely non-obvious operational context — wind is in knots and times are local to the location — which an agent cannot get from the annotations or schema. Return shape is left to the output schema, which is acceptable since one exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability first, then when to use, then units/timezone caveats, then the alternative. Every sentence carries information an agent needs and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only forecast tool with full schema coverage, annotations and an output schema, the description covers the remaining gaps that matter: units, timezone semantics and sibling routing. An agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters (hours, latitude, longitude, location) are already documented, including ranges and the lat/lon-overrides-location rule. The description adds only 'for a place', which does not extend parameter meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'current conditions plus an hourly forecast' with the exact variables returned (temperature, rain, cloud, wind). It also differentiates itself from the wind-focused siblings by name, so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit positive trigger ('use for general what's-the-weather questions') and an explicit exclusion with named alternatives ('for wind-sport planning prefer get_wind_forecast or find_wind_windows'). Nothing about routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server