Skip to main content
Glama

marine

by io.github.pipeworx-io

Get Current Waves

get_current_waves
Read-onlyIdempotent

Check real-time wave conditions at a coastal location. Returns current wave height, period, and direction. Use for immediate surfing, boating, or maritime planning decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location.
longitudeYesLongitude of the location.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location
longitudeYesLongitude of the location
wave_height_mYesCurrent wave height in meters
wave_period_sYesCurrent wave period in seconds
wave_direction_degYesCurrent wave direction in degrees

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "latitude": {
+      "description": "Latitude of the location",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Longitude of the location",
+      "type": "number"
+    },
+    "wave_direction_deg": {
+      "description": "Current wave direction in degrees",
+      "type": "number"
+    },
+    "wave_height_m": {
+      "description": "Current wave height in meters",
+      "type": "number"
+    },
+    "wave_period_s": {
+      "description": "Current wave period in seconds",
+      "type": "number"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude",
+    "wave_height_m",
+    "wave_period_s",
+    "wave_direction_deg"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 21.3099,
+    "longitude": -157.8581
+  },
+  {
+    "latitude": 34.0195,
+    "longitude": -118.4912
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the behavioral detail that it returns real-time wave fields, but it does not go beyond that to mention data sources, latency, or edge cases. With annotations covering the safety profile, the added context is sufficient but not rich.

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 concise sentences, each earning its place: purpose, output fields, and usage context. The key information is front-loaded and there is no wasted wording.

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 tool with full schema coverage, rich annotations, and an output schema, the description is properly scoped. It covers the purpose, key output, and usage scenarios, though it could mention the forecast alternative explicitly to be entirely complete.

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?

The input schema provides 100% coverage for both parameters (latitude and longitude). The description adds no additional parameter-level meaning beyond the schema, so the baseline score of 3 applies.

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 states the verb ('Check'), resource ('real-time wave conditions'), and scope ('coastal location'), and specifies the output ('wave height, period, and direction'). It clearly distinguishes from the sibling get_wave_forecast by emphasizing 'current' and 'real-time' for immediate decisions.

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 context for when to use the tool: 'use for immediate surfing, boating, or maritime planning decisions.' It does not explicitly name the alternative (get_wave_forecast) or state when not to use it, but the 'current' vs 'forecast' distinction is strongly implied.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have distinct purposes, but some overlap exists in the prediction market area (e.g., bet_research vs. polymarket_edges vs. polymarket_arbitrage) and in AI visibility checks. Descriptions help differentiate, but confusion is possible.

Naming Consistency3/5

Names mix verb_noun (ask_pipeworx, generate_llms_txt) and noun_verb patterns (entity_profile, polymarket_edges). While some groups are consistent individually, the overall naming lacks a uniform convention.

Tool Count4/5

With 32 tools covering a broad domain (data lookup, prediction markets, memory, subscriptions), the count is slightly high but still reasonable for the scope. Each tool has a specific role.

Completeness4/5

The tool set is comprehensive for the stated domain, including data retrieval, entity analysis, comparisons, research, and prediction markets. Minor gaps exist (e.g., no direct CRUD for user data besides memory), but the surface is mostly complete.

Resources