Skip to main content
Glama

thirdtrail

by io.github.thirdtrail
OverviewDiscussionsAdmin

Tide height series

get_tide_heights
Read-onlyIdempotent

Water height at a coastal point at a fixed step: a list of time and height_m pairs. Use it to plot a tide curve or read the height at a particular time; for just the highs and lows use get_tide_extremes. Metres relative to mean sea level, not chart datum. Defaults: from today, 2 days, and the finest step the plan allows, but no finer than 10m. Requires an API key on a paid Tides plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tzNoIANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees.
daysNoNumber of days to return. The ceiling is plan-dependent.
stepNoSampling interval. Finer steps need a higher plan.
start_dateNoFirst day as YYYY-MM-DD. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / step / description
      Previous value: -"Sampling interval, e.g. 10m, 1h. Finer steps are plan-gated."New value: +"Sampling interval. Finer steps need a higher plan."
    • addedInput schema / properties / step / enum
      Added value: +[
+  "1m",
+  "5m",
+  "10m",
+  "15m",
+  "30m",
+  "1h"
+]
    • changedInput schema / properties / tz / description
      Previous value: -"IANA timezone for output timestamps, e.g. Europe/Dublin."New value: +"IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningfully beyond that: the datum caveat ('metres relative to mean sea level, not chart datum'), the three default behaviors, the plan-dependent step floor (no finer than 10m), and the auth/plan requirement.

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?

Three sentences, each doing distinct work: shape, usage/alternative, constraints. Front-loaded with what is returned, with no filler or restated field names.

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 no output schema, the description still characterizes the return as time/height pairs. Combined with 100% schema coverage and disclosed auth/plan and datum constraints, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description supplies default values the schema omits for start_date, days, and step ('from today, 2 days, and the finest step the plan allows, but no finer than 10m'). It does not add units or format detail for tz/lat/lon beyond the schema, so it is not a full 5.

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?

States a specific verb+resource with the exact return shape ('a list of time and height_m pairs'), and explicitly contrasts itself with the sibling get_tide_extremes. An agent can distinguish it from get_tide_window and get_tide_extremes without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete use cases ('plot a tide curve or read the height at a particular time') and an explicit routing rule: 'for just the highs and lows use get_tide_extremes'. It also names the access prerequisite (API key on a paid Tides plan), which is a selection constraint in practice.

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

All thirdtrail 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