Skip to main content
Glama
Sign In

Tide Times and Tide Tables MCP

by io.github.theluckystrike
OverviewDiscussionsAdmin

Low tide windows

low_tide_windows
Read-onlyIdempotent

Find the low tides at or below a height over the coming days, marked daylight or dark, for tide pooling, clamming, beach access or launching a boat. Up to 90 days ahead.

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": {
      "location": "<location>"
    },
    "name": "low_tide_windows"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays to scan from today, 1 to 90. Default 7.
unitsNoenglish = feet (default), metric = metres.
locationYesPlace like "Santa Cruz, CA" or "Cape May, NJ", a NOAA station id like 9414290, or "lat,lon".
max_heightNoOnly lows at or below this height (feet or metres per units). Default 0.5 ft or 0.15 m.
daylight_onlyNoOnly lows between sunrise and sunset. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, open-world behavior, so the safety burden is covered. The description adds real context beyond them: results are tagged daylight vs dark, the scan horizon is capped at 90 days, and the output is a filtered window list. It does not describe ordering, pagination, or what happens when no lows qualify.

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?

Two short sentences, front-loaded with the core action and filtering rule, then the horizon limit. Every clause carries usable information; no filler or restated name/title.

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 read-only, single-object-schema tool with full parameter coverage and no output schema, the description covers purpose, filter semantics, use cases, and the 90-day bound. Remaining gaps are minor: no statement of result ordering, empty-result behavior, or how 'dark' is defined.

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?

With 100% schema description coverage, all five parameters (days, units, location, max_height, daylight_only) are already documented including defaults and bounds. The description only implies max_height ('at or below a height') and daylight_only ('marked daylight or dark') without adding syntax or format meaning beyond the schema.

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 and resource ('Find the low tides') plus a distinguishing scope constraint ('at or below a height'), an output attribute ('marked daylight or dark'), and a horizon ('Up to 90 days ahead'). The threshold-filtered framing separates it cleanly from tide_now and tide_times without needing to name them.

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?

Gives concrete usage contexts ('tide pooling, clamming, beach access or launching a boat') that tell an agent when this tool is the right choice. It offers no explicit exclusions or named alternatives (e.g., when to prefer tide_times for high tides or full tables), so it stops short of a 5.

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

All Tide Times and Tide Tables MCP 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