Skip to main content
Glama
Sign In

Tide Times and Tide Tables MCP

by io.github.theluckystrike
OverviewDiscussionsAdmin

Find NOAA tide stations

tide_stations_search
Read-onlyIdempotent

Find NOAA tide prediction stations by name ("Monterey", "Bar Harbor, ME") or nearest to lat,lon, with station id, state, type and distance. Use the id with the other tide tools when a place name is ambiguous.

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": {
      "query": "<query>"
    },
    "name": "tide_stations_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum stations, 1 to 25. Default 10.
queryYesStation or place name, optionally with state ("Newport, RI"), or "lat,lon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the return payload (station id, state, type, distance) and by warning that name matches can be ambiguous, though it says nothing about the cap of 25 results or ranking of "nearest" matches.

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 tight sentences: the capability and accepted inputs are front-loaded, followed by one actionable usage note. No filler, no restatement of the title.

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 only two parameters, full schema coverage, and no output schema, the description fills the one real gap by enumerating the returned fields. An agent has everything needed to decide to call it and to interpret the response.

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 description coverage is 100%, so both parameters are already documented, including the "Newport, RI" and "lat,lon" formats. The description restates the same formats with different examples rather than adding new semantics (no note on how distance is computed, how ties are broken, or how limit interacts with the query).

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?

The description states a specific verb and resource ("Find NOAA tide prediction stations") plus the two accepted lookup modes (place name or lat,lon) and the fields returned. It implicitly separates itself from the sibling data tools by positioning itself as the station-id resolver, but never names a sibling explicitly.

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?

It gives a clear routing rule: use the returned id with "the other tide tools" when a place name is ambiguous, which tells the agent this is the resolution step before calling tide_now/tide_times. It stops short of an explicit when-not-to-use statement (e.g. "do not use to get tide heights").

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