Skip to main content
Glama

get_tidal_stream

Read-onlyIdempotent

The tidal stream and the tide at one point, from the tidal atlases alone.

    For the questions about a pass or a harbour entrance: when to be at
    the Raz de Sein to carry the stream, when the Fromveur turns, how
    hard it runs at Port-Navalo tomorrow, when high water is at Chausey.
    Costs no weather request: harmonic predictions from the atlases this
    server ships (SHOM, MARC and others), the same ones ``plan_passage``
    applies leg by leg.

    Args:
        lat: latitude in degrees, at sea, in the pass itself.
        lon: longitude in degrees.
        start: ISO-8601 datetime with the user's UTC offset; every time
            in the answer comes back in that offset.
        end: ISO-8601 datetime, timezone-aware. At most 400 steps.
        heading_deg: optional course through the point (true degrees,
            the direction you head to). With it, each step gets
            ``along_kn`` (positive: the stream carries you, negative: it
            stems you) and the answer lists the ``favourable`` and
            ``adverse`` windows.
        step_minutes: 5 to 180, default 30.

    Returns ``covered``, ``source``, ``confidence``, ``points`` (a table:
    ``columns`` time, ``speed_kn``, ``direction_to_deg`` it flows to,
    ``along_kn``, ``height_m`` around mean sea level; one row per step),
    ``slack`` (the moments the stream nearly
    stops), ``high_waters`` / ``low_waters``, ``favourable`` /
    ``adverse`` when a heading is given, ``tide_coefficient`` (French
    national coefficient, Brest, on French atlases), a ``warning`` when
    the atlas does not resolve the pass, and ``openwind_url``.

    Outside every atlas (most of the Mediterranean, the open sea)
    ``covered`` is false: say so, and use ``get_marine_forecast``, which
    returns the global model's current where it matters.

    Astronomical tide only: no surge, no wind-driven current. The windows
    are facts about the stream, not a recommendation: weigh them against
    the wind (``get_marine_forecast``) and the whole passage
    (``plan_passage``). Present the answer yourself, the time to be at the
    pass in one sentence and the few times that back it: no widget comes
    with this tool.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
latYes
lonYes
startYes
heading_degNo
step_minutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description adds substantial context beyond them: no weather request is consumed, predictions are astronomical only (no surge, no wind-driven current), a warning appears when the atlas fails to resolve the pass, and no widget is returned so the agent must present the answer itself. These are genuine behavioral disclosures, not restatements.

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 purpose and usage, then cleanly split into Args and Returns sections. It is long, and the Returns paragraph partly mirrors what the output schema likely already carries, so it is slightly more verbose than strictly necessary, but every line is informative and earns its place.

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 six-parameter tool with an output schema, the description is complete: it covers the coverage/fallback rule, the astronomical-only limitation, the presentation responsibility, and the effect of every optional parameter. An agent has everything needed to call it correctly and interpret the response.

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

Parameters5/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 and does: lat/lon semantics ('at sea, in the pass itself'), start as ISO-8601 with the user's UTC offset governing all returned times, end's 400-step cap, heading_deg's effect on along_kn and favourable/adverse windows, and step_minutes' 5-180 range with default 30. Each parameter gains meaning absent from 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: retrieves the tidal stream and tide at one point, sourced solely from the tidal atlases the server ships. It immediately distinguishes itself from get_marine_forecast (weather model) and plan_passage (whole passage), so an agent can identify the tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives concrete use cases (when to be at the Raz de Sein, when the Fromveur turns, high water at Chausey) and explicit routing: when the point is outside every atlas, say so and use get_marine_forecast; for the whole passage it points to plan_passage. Both the when-to-use and the alternatives are stated.

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.