Skip to main content
Glama

US tide predictions (NOAA, x402)

Ocean tide forecast for a US coastal point: the next 48 hours of high and low tides (time, height in feet and metres) fr

us_tide_predictions
Read-onlyIdempotent

Ocean tide forecast for a US coastal point: the next 48 hours of high and low tides (time, height in feet and metres) from the nearest NOAA tide station to your lat/lon, or for a station id (lat=40.70, lon=-74.01 or station=8518750). For boating, fishing, surf, coastal logistics and travel agents. Pay per call $0.01 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
latNolatitude of the coastal point, e.g. 40.70
lonNolongitude, e.g. -74.01
stationNoor a 7-digit NOAA station id, e.g. 8518750
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

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 cover read-only, idempotent, open-world and non-destructive behavior, so the description only needs to add beyond that — and it does, disclosing the $0.01 USDC Base x402 cost and that lat/lon is resolved to the *nearest* station (a behavioral detail with real accuracy implications). Payment-flow mechanics are left to the schema but the cost model, the key unknown for an agent, is stated up front.

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?

Front-loaded with the resource and scope, then use cases, then pricing — nothing extraneous. The first sentence is long and run-on with parenthetical examples, which slightly hurts scannability but wastes no words.

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?

Four optional parameters, no output schema and rich annotations mean the definition needs mainly scope, coverage and payment posture — all present (48-hour horizon, US-only, feet/metres, per-call price). Minor gap: no statement about behavior when no station is near the point, or what happens if neither lat/lon nor station is supplied despite zero required parameters.

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 lat, lon, station and x_payment are already documented with examples; the description's coordinate and station examples largely duplicate that. The one genuine addition is framing lat/lon and station as alternative addressing modes resolved to a nearest station, which is modest value over 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 (tide forecast) plus tight scope: next 48 hours of high/low tides, time and height in feet and metres, nearest NOAA station, US coastal points. An agent can distinguish this from siblings like weather_forecast without 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?

Gives clear context for when to reach for it (boating, fishing, surf, coastal logistics, travel agents) and names two valid input modes — coordinate pair or station id. It stops short of explicit exclusions or pointing to a sibling tool for non-US or non-tide cases, so it falls just below a 5.

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