Skip to main content
Glama

Tide predictions for 1 to 7 days at the NOAA station

tides
Read-only

Tide predictions (high and low water, metres above MLLW, UTC times) for 1 to 7 days at the NOAA station nearest a point, or at a station id, from NOAA CO-OPS (US public domain). Give lat and lon, or a place name. Coverage is US coasts, Great Lakes and territories only; a point more than 100 km from a station is a 404, not charged. search=name lists stations. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tides"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (with lon)
lonNoLongitude (with lat)
daysNoDays of predictions, 1 to 7, default 2
placeNoPlace name, geocoded (instead of lat and lon)
searchNoName fragment to list stations instead of predictions, at least 3 characters
stationNoNOAA station id, 7 digits, e.g. 8518750 (one of station, place, lat and lon, or search)

Output Schema

NameRequiredDescriptionDefault
daysNo
countNo
datumNo
pointNo
sourceNo
stationNo
coverageNo
checkedAtNo
predictionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses pricing ($0.002 per successful call), the payment rail (x402, USDC on Base/Solana/others), that failed calls are not charged, and the geographic coverage limit that produces a 404. That is exactly the behavioral context an agent needs before deciding to spend money.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: what it returns, then how to specify location, then coverage limits, then price. The payment-rail detail is the longest clause, but it is decision-relevant for a paid tool, so little is wasted.

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?

For a read-only, open-world lookup with a full parameter schema and an output schema, the description covers everything an agent needs: data semantics, location input alternatives, coverage boundary, error behavior, and cost. Return-value formatting is correctly left to the output schema.

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 already 100%, so the schema carries the parameter burden, but the description adds real meaning by framing station, place, lat/lon, and search as mutually exclusive input strategies rather than independent fields. It also reinforces the units and time base (metres above MLLW, UTC) that the schema does not express.

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?

The description gives a specific verb and resource — tide predictions (high/low water, metres above MLLW, UTC) — plus scope (1–7 days) and the two ways to locate a station (nearest point or station id). The data source (NOAA CO-OPS) and coverage area are stated, so an agent knows exactly what this returns before opening the schema.

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 tells the agent how to pick an input mode: give lat and lon, or a place name, or a station id, and use search=name to list stations instead of getting predictions. It also states a concrete failure condition (a point more than 100 km from a station returns a 404). What it does not do is name when another tool would be preferable, though no obvious sibling overlaps are implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources