Skip to main content
Glama
Sign In

Tide Times and Tide Tables MCP

by io.github.theluckystrike
OverviewDiscussionsAdmin

High and low tide times

tide_times
Read-onlyIdempotent

High tide and low tide times and heights (a tide table) for a US coastal place or NOAA station, today or any date, from NOAA tide predictions. location takes a place ("Santa Cruz, CA"), a NOAA station id (9414290) or lat,lon. Up to 31 days per call.

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": "tide_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFirst day, YYYY-MM-DD in station local time. Default today at the station.
daysNoNumber of days, 1 to 31. Default 1.
unitsNoenglish = feet (default), metric = metres.
locationYesPlace like "Santa Cruz, CA" or "Cape May, NJ", a NOAA station id like 9414290, or "lat,lon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: the US-coastal-only restriction, the NOAA data source, and the hard cap of 31 days per call — real constraints an agent cannot infer from annotations.

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 tight sentences: what it returns, where the data comes from, accepted location formats, then the call limit. No filler and the most useful scoping facts lead.

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 a tide table of times and heights, and annotations carry the safety profile. For a simple 4-parameter read tool, nothing needed to invoke it correctly is missing.

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 coverage is 100%, so date, days, units, and location are already documented with defaults and limits. The description reinforces the accepted location formats and the 31-day ceiling but adds little syntax or format detail beyond the schema, making the baseline 3 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 resource (high/low tide times and heights, i.e. a tide table), its source (NOAA tide predictions), and its geographic scope (US coastal place or NOAA station). The 31-day-per-call note implicitly separates it from single-instant siblings like tide_now, but no sibling is named explicitly.

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?

Usage is implied rather than stated: the multi-day table framing and 'today or any date' suggest when to reach for this over tide_now or low_tide_windows, but no explicit when-to-use or when-not-to-use instruction is given.

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