Skip to main content
Glama

Marine Swell Forecast

marine.ocean.swell
Read-onlyIdempotent

Hourly swell forecast at an ocean coordinate — swell wave height (m), swell direction (°), and swell period (s) for up to 16 days. Swell consists of wind-generated waves that have propagated far from their origin, typically with longer periods (>10s) and more regular patterns than wind-sea. High-period swell (>12s) is ideal for surfing; low-period swell (<6s) indicates local chop. Swell direction indicates where the swell is coming from (degrees clockwise from north). Useful for surf forecasting, sailing passage planning, and aquaculture site assessment. Source: Open-Meteo Marine API, CC BY 4.0, no authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude 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.
timezoneNoTimezone for the returned time values (e.g. "UTC", "Europe/London", "America/New_York"). Defaults to UTC.
longitudeYesLongitude of the ocean location in decimal degrees (e.g. -14.0 for Atlantic, 2.3 for North Sea).
forecast_daysNoNumber of days to forecast (1–16). Defaults to 7. Hourly data is returned for each day.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool 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.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent hints. The description adds the source, licensing, and no-authentication requirement, which is useful context beyond the annotations. It does not mention potential errors or rate limits, but given the annotations cover safety, this is adequate.

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?

The description is well-structured, starting with the core purpose and then layering explanatory and contextual details. Every sentence adds value, and it is not overly verbose despite being thorough.

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?

With an output schema present, the description does not need to detail return structures. It covers data units, time range, use cases, and source/auth, making it complete for an agent to call correctly. Any limitations (e.g., null on land) are captured in the schema.

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 each parameter has a detailed description with examples. The tool description adds context about swell direction meaning and period thresholds, but these apply to outputs rather than input parameters. It does not add significant new information about the parameters themselves.

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 provides hourly swell forecasts at a coordinate, listing the exact output metrics (height, direction, period) and range (up to 16 days). It also distinguishes swell from wind-sea, making it distinct from siblings like marine.ocean.waves.

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, sailing, aquaculture) and explains swell interpretation (high vs low period), which helps an agent decide when this tool is relevant. However, it does not explicitly contrast with sibling tools or state when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.