Skip to main content
Glama

marine_forecast

Read-onlyIdempotent

Retrieve ocean wave, swell, and marine weather forecasts for a latitude and longitude, with up to 16 days of forecast data for planning marine activities.

Instructions

Get ocean wave, swell, and marine weather forecast for a location.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "marine_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude of the ocean point.
longitudeYesLongitude of the ocean point.
forecast_daysNoNumber of forecast days (default 7, max 16).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond those annotations, such as return granularity, units, data source, or how the forecast horizon behaves.

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?

A single front-loaded sentence with no wasted words. It efficiently communicates the core resource and scope.

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?

For a simple read-only forecast tool with a fully described three-parameter schema and rich safety annotations, the description is nearly complete. Minor gaps remain around units and the exact nature of the forecast output, but these are not critical for invocation.

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 latitude, longitude, and forecast_days all documented directly in the schema. The description does not add meaning beyond the schema, so the baseline of 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?

States a specific verb and resource: getting ocean wave, swell, and marine weather forecasts. The marine/ocean focus distinguishes it from general weather siblings, though it does not explicitly name an alternative like weather_forecast or willyweather_surf.

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

Usage Guidelines3/5

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

The phrase "for a location" and the marine-specific data imply usage for ocean points, but there is no explicit guidance on when to use this versus general weather, surf, or tide tools. Usage is inferable but not stated.

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

Deploy Server

Other Tools