Skip to main content
Glama

Marine

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Wave Forecast

get_wave_forecast
Read-onlyIdempotent

Get multi-day wave forecasts for coastal locations (e.g., "Hawaii", "California Coast"). Returns max wave height, period, and dominant direction per day. Use when planning water activities or monitoring upcoming swell.

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of forecast days (1-7, default 7).
latitudeYesLatitude of the location.
longitudeYesLongitude of the location.

Output Schema

NameRequiredDescriptionDefault
daysYesArray of daily wave forecast objects
latitudeYesLatitude of the location
longitudeYesLongitude of the location

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "days": {
+      "description": "Array of daily wave forecast objects",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Forecast date",
+            "type": "string"
+          },
+          "wave_direction_dominant_deg": {
+            "description": "Dominant wave direction in degrees",
+            "type": "number"
+          },
+          "wave_height_max_m": {
+            "description": "Maximum wave height in meters",
+            "type": "number"
+          },
+          "wave_period_max_s": {
+            "description": "Maximum wave period in seconds",
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "wave_height_max_m",
+          "wave_period_max_s",
+          "wave_direction_dominant_deg"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "latitude": {
+      "description": "Latitude of the location",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Longitude of the location",
+      "type": "number"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude",
+    "days"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "days": 5,
+    "latitude": 21.3099,
+    "longitude": -157.8581
+  },
+  {
+    "latitude": 34.0195,
+    "longitude": -118.4912
+  }
+]
  3. First observed

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, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds return details (max wave height, period, direction per day) and the multi-day scope, going beyond what annotations provide. No contradictions.

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 three sentences, front-loaded with the main purpose, then return values, then usage guidance. Every sentence earns its place with no redundancy or fluff.

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?

Given low complexity, rich annotations, 100% schema coverage, and an output schema, the description is mostly complete. It covers purpose, return values, and usage. However, the examples 'Hawaii', 'California Coast' might misleadingly suggest string locations are accepted, while the schema requires numeric latitude/longitude, a minor gap.

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% and each parameter (days, latitude, longitude) has a descriptive entry. The tool description does not add further parameter semantics, but the schema already provides sufficient detail, aligning with the baseline score of 3.

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: 'Get multi-day wave forecasts for coastal locations' with examples. It distinguishes from the sibling 'get_current_waves' by explicitly saying 'multi-day' as opposed to current conditions.

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 usage context: 'Use when planning water activities or monitoring upcoming swell.' It does not explicitly name alternative tools or exclusion scenarios, but the context is sufficiently clear for an agent to decide when to invoke this tool.

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

All Marine toolsInspect
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.

Resources