apibase

Marine Wave Conditions Forecast

marine.ocean.waves

Read-onlyIdempotent

Hourly wave conditions forecast at an ocean coordinate — wave height (m), wave direction (°), and wave period (s) for up to 16 days. Wave height is significant wave height (average of the highest third of waves). Wave direction is the mean direction from which waves are coming (degrees clockwise from north). Wave period is the mean time between successive wave crests in seconds. Useful for surfing spot reports, ferry/vessel routing, coastal engineering assessments, and storm monitoring. Source: Open-Meteo Marine API, CC BY 4.0, no authentication required.

Input Schema

TableJSON Schema

Name	Required	Description
`latitude`	Yes	Latitude of the ocean location in decimal degrees (e.g. 51.5 for English Channel, 48.5 for Bay of Biscay). Must be over open water — land coordinates return null values.
`timezone`	No	Timezone for the returned time values (e.g. "UTC", "Europe/London", "America/New_York"). Defaults to UTC.
`longitude`	Yes	Longitude of the ocean location in decimal degrees (e.g. -14.0 for Atlantic, 2.3 for North Sea).
`forecast_days`	No	Number of days to forecast (1–16). Defaults to 7. Hourly data is returned for each day.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond that: precise definitions of significant wave height, wave direction origin and units, wave period semantics, hourly cadence, data source (Open-Meteo Marine API), license (CC BY 4.0), and no authentication requirement — all useful for an agent deciding whether and how to call.

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 information-dense sentences with no waste: core capability first, then metric definitions, then use cases and provenance. It avoids repeating schema content and front-loads the operational essentials, making it easy for an agent to scan.

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?

An output schema is present, so the description need not enumerate return fields. It supplies source, license, authentication status, metric semantics, and use cases, while the schema covers coordinate constraints, defaults, and the 16-day limit. Nothing needed for correct invocation is missing.

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%, with each parameter documented with defaults, examples, and constraints. The description mentions the hourly cadence and 16-day horizon, which aligns with forecast_days but adds no new parameter-level meaning beyond the schema. Per the baseline rule for high coverage, 3 is appropriate.

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?

The description states a specific resource (hourly wave conditions forecast at an ocean coordinate), the specific metrics returned (wave height, direction, period), and the forecast horizon (up to 16 days). It distinguishes from sibling marine tools by enumerating the wave parameters, though it stops short of explicitly naming alternatives like marine.ocean.swell or marine.ocean.temperature.

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?

The description lists concrete use cases (surfing spot reports, ferry/vessel routing, coastal engineering, storm monitoring) that tell an agent when this tool is relevant. It does not explicitly exclude alternatives or name sibling tools, so it falls short of the full 5 for explicit when-not/alternative guidance.

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

All apibase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.