Skip to main content
Glama
Sign In

Tide Times and Tide Tables MCP

by io.github.theluckystrike
OverviewDiscussionsAdmin

Tide right now

tide_now
Read-only

Is the tide coming in or going out right now at a US coastal place? Returns rising or falling, the estimated current height, and the time and height of the next high and next low tide, from NOAA predictions.

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_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false, so safety and repeat-call behavior are covered structurally. The description adds provenance (NOAA predictions) and the shape of the answer, which is real value, but it says nothing about data freshness, station resolution failures, or ambiguity handling for a loosely specified location.

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 sentences, the core question front-loaded, followed by a compact enumeration of the returned values and the data source. No filler and nothing redundant with structured fields.

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?

With no output schema, the description carries the return-value burden and does so well by naming the four returned quantities. For a simple two-parameter read tool the gaps (units handled by schema, error behavior on unresolvable stations) are minor.

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% and both parameters are well documented there, so the baseline is 3. The description earns an extra point by adding a constraint the schema does not state: the location must be a US coastal place, which meaningfully narrows how the location string should be formed.

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?

"Is the tide coming in or going out right now at a US coastal place?" states a specific question plus scope (current, US coastal) and then enumerates exactly what is returned (rising/falling, current height, next high/low time and height). That 'right now' framing implicitly separates it from tide_times and low_tide_windows, but no sibling is named, so it falls just short of the top tier.

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 by the question form and the 'US coastal place' restriction, which effectively excludes non-US or inland queries. However, it never states when to prefer tide_times or low_tide_windows instead, nor what to do for non-US locations.

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