apibase

Marine Comprehensive Forecast

marine.ocean.forecast

Read-onlyIdempotent

Full hourly marine forecast at any ocean coordinate up to 16 days ahead. Returns all marine variables: significant wave height (m), mean wave direction (°), mean wave period (s), swell wave height (m), swell direction (°), swell period (s), and sea surface temperature (°C). Data is sourced from CMEMS ERA5 reanalysis and global wave models (ERA5-Ocean, MEPS, GFS). Ideal for offshore operations, ship routing, marine research, and multi-variable coastal planning. Supply latitude/longitude of an open-ocean or coastal point; land coordinates return null values. 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true)Skip. The description adds useful beyond-schema behavioral context: data sources (CMEMS ERA5, ERA5-Ocean, MEPS, GFS), land coordinates returning null, and licensing/auth-free access. This enriches the agent's understanding without contradicting annotations.

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

Conciseness4/5

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

The description is a single paragraph with six purposeful sentences: core functionality, variable list, data sources, use cases, input guidance, and attribution. Each sentence earns its place, though the variable list is lengthy and could be considered dense. No fluff.

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?

Given the output schema exists and annotations cover safety, the description provides comprehensive guidance: purpose, variables, data source, use cases, input constraints (land = null), licensing, and authentication status. No critical information needed to invoke the tool correctly 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 coverage is 100% and parameter descriptions in the schema are detailed (e.g., latitude 'land coordinates return null values' and forecast_days 'Defaults to 7'). The description adds no extra parameter semantics beyond summarizing that latitude/longitude are needed. This meets the baseline for full schema coverage.

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?

The description clearly states the tool's function: 'Full hourly marine forecast at any ocean coordinate up to 16 days ahead' with a specific list of returned variables. It distinguishes itself from sibling tools like marine.ocean.waves by framing this as the comprehensive forecast ('all marine variables').

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 provides clear use cases: 'Ideal for offshore operations, ship routing, marine research, and multi-variable coastal planning.' It implies a multi-variable need but does not explicitly contrast with single-variable sibling tools, nor does it state when NOT to use this tool. No explicit alternatives are mentioned.

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.