WindWise MCP

Waves, swell and sea temperature

get_marine_conditions

Read-onlyIdempotent

Fetches coastal or offshore marine forecasts with wave, swell, sea temperature, and current data, plus daily sea-state ratings and beginner-friendly flags for trip planning.

Instructions

Marine forecast for a coastal location: wave height and period, swell height/direction/period, sea surface temperature and ocean current. Each day includes a sea-state rating and whether it is beginner-friendly. Only works for coastal or offshore points; inland places return an error.

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_marine_conditions"
  }
}

Input Schema

Name	Required	Description
`days`	No	Number of days to cover, starting now (1-7). Hours already past are left out.
`end_hour`	No	End of the time range, local hour 1-24 (exclusive): 18 means up to 18:00.
`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.
`start_hour`	No	Start of the time range, local hour 0-23 (inclusive).

Output Schema

Name	Required	Description
`daily`	Yes
`hours`	Yes
`units`	Yes
`caveat`	Yes
`hourly`	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.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and network behavior are covered. The description adds value beyond that by disclosing the inland-point error behavior and the per-day sea-state rating / beginner-friendly output, which the agent cannot infer from annotations. No data source, latency, or unit conventions are mentioned.

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 short sentences, front-loaded with the tool's identity and output content, then the geographic constraint. No filler and no redundancy with the title or schema.

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

Completeness4/5

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

An output schema exists, so it is acceptable that return contents are only summarized; all parameters are optional and fully described. The remaining gap is that wave height, period, and temperature units are never stated anywhere in the definition, which matters for a marine forecast.

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 six parameters (days, start_hour, end_hour, latitude, longitude, location) are already fully documented in the schema, including the coordinate-over-location precedence. The description adds no syntax, format, or unit detail beyond that, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource ("Marine forecast for a coastal location") and enumerates the exact quantities returned: wave height/period, swell height/direction/period, SST, and currents. This inherently separates it from the land-weather siblings like get_weather and get_wind_forecast, though it never names them explicitly.

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

Usage Guidelines4/5

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

Gives a clear applicability condition (coastal or offshore points only) and a concrete failure mode (inland places return an error), which is genuine when-not guidance. It stops short of routing the agent to an alternative tool for inland points, which would be needed for a 5.

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

Deploy Server