Solano — marine & outdoor weather

Tides

get_tide

Read-onlyIdempotent

High and low water times and tidal range at any point on the globe, and real water heights wherever a national almanac covers it.

Two very different answers, and the difference matters:

- `reference.kind == "chart_datum"` — a national tide almanac is attached to
  this point (Canada CHS, France api-maree.fr, Ireland Marine Institute).
  `height_m` is then a TRUE water height above chart datum, which can be
  added to a charted sounding.
- `reference.kind == "lowest_low_water"` — no almanac here, so the figures
  come from a global model referenced to mean sea level. Times and ranges
  are sound (they are differences, the unknown datum cancels out) but
  `height_m` is NOT a water height: it is an offset above an internal
  reference. Never add it to a sounding, and never present it as depth.

Model range is systematically UNDERSTATED, the more so the more confined the
place (-6% Halifax, -20% at the head of the Bay of Fundy): 8 km grid cells do
not resonate a funnel. This is flagged, never silently corrected.

The almanac attachment for a new point is decided in the background, so the
first call at a fresh location may return the model and a later one the
almanac.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`latitude`	Yes
`longitude`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4/5.0

Behavior5/5

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

Far exceeds the annotations: it discloses the two datum regimes, the semantic meaning of height_m under each, a quantified systematic underestimation bias (-6% Halifax, -20% Bay of Fundy) that is flagged rather than silently corrected, and the fact that almanac attachment is resolved asynchronously so a fresh location may change its answer between calls. This is exactly the context annotations cannot carry.

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 core capability, then cleanly bulleted into the two reference kinds and the caveats. It is longer than average but nearly every line carries distinct operational value; the three-paragraph caveat block could be tightened slightly.

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 does the heavy lifting on return semantics and does it well, explaining what height_m means in each mode and what must never be done with it. The gap is input-side: days and coordinate conventions are unexplained anywhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it says nothing about latitude/longitude format (decimal degrees? sign convention?) and never mentions the `days` parameter or its default of 3. Only the vague phrase 'any point on the globe' hints at the coordinate inputs.

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 ('High and low water times and tidal range at any point on the globe') plus the two possible result modes (chart_datum vs lowest_low_water). An agent can tell instantly this is the tide-height tool and not a forecast, bulletin or anchorage tool, even 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description is rich in how to interpret and how NOT to use the output (never add height_m to a sounding), but it never says when to call this versus siblings like get_forecast or analyze_anchorage, nor prerequisite conditions. Usage is implied by the tool's domain rather than stated as a routing rule.

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

All Solano — marine & outdoor weather tools Inspect

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

Need Help?