Skip to main content
Glama

Open Meteo Marine

open_meteo_marine
Read-onlyIdempotent

"Wave / swell / surf forecast for [beach]" / "sea conditions in [bay]" / "wave height at [coordinates]" / "is it safe to sail", global marine weather forecast (wave height, wave period, wave direction, wind waves, swell waves) at any ocean lat/lng. Free, keyless. Use for surf reports, sailing prep, fishing conditions, coastal planning.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": 37.7749,
      "longitude": -122.4194
    },
    "name": "open_meteo_marine"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourlyNoDefault wave_height,wave_period,wind_wave_height
latitudeYes
longitudeYes
forecast_daysNo

Output Schema

NameRequiredDescriptionDefault
hourlyNoHourly marine forecast data
latitudeNoQuery latitude
timezoneNoIANA timezone string
elevationNoElevation of the location in meters
longitudeNoQuery longitude
hourly_unitsNoUnits for hourly marine variables
generationtime_msNoAPI response generation time in milliseconds
utc_offset_secondsNoUTC offset in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world behavior, so the description isn't obligated to re-state safety. It still adds real value beyond them by disclosing 'Free, keyless' (no authentication/setup cost) and confirming truly global coverage at any ocean coordinate — both material to whether an agent can call it directly. It stops short of unit conventions or rate/limit behavior for the API.

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

Conciseness3/5

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

The content is dense and front-loaded, but the leading block of slash-separated quoted phrases reads like keyword bait rather than prose and pushes the actual statement of purpose to the second sentence. Every element is arguably useful for retrieval matching, yet the slash-and-quote formatting makes it slower to parse than a straight declarative sentence.

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?

With an output schema present, the description needn't explain return values, and the annotations cover the safety profile, so the remaining burden is modest and mostly met by the domain coverage and keyless note. The notable gap is guidance on the optional 'forecast_days' and 'hourly' parameters, which neither the description nor the sparse schema explains clearly.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description needs to compensate and largely does not. It mentions only 'lat/lng' implicitly and says nothing about 'forecast_days' (horizon length) or the 'hourly' variable-selection string, whose default list is buried in the schema. An agent can construct a minimal call but cannot reason about multi-day horizons or custom variable sets from the description.

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 names a specific resource and domain — 'global marine weather forecast (wave height, wave period, wave direction, wind waves, swell waves) at any ocean lat/lng' — and the leading quoted query patterns ('wave height at [coordinates]', 'is it safe to sail') make the intended use unmistakable. It does not explicitly contrast itself with the sibling open_meteo_forecast or open_meteo_air_quality, so an agent must infer the marine-vs-terrestrial boundary from the word 'marine' alone.

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?

Concrete use cases are spelled out: 'surf reports, sailing prep, fishing conditions, coastal planning', which tells an agent when this tool is the right pick. There are no explicit exclusions or named alternatives, so guidance is clear on when-to-use but silent on when-not-to-use.

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.