Skip to main content
Glama

Coastal planning window

get_tide_window
Read-onlyIdempotent

Per day: high and low waters together with sunrise, sunset, golden and blue hour, twilight and moon phase in a single call. The planning tool for coastal photography, fishing and shore work; use it instead of calling get_tide_extremes and get_sun_moon_times separately. Pass elevation when you know it: it shifts the sun and moon times — roughly three minutes at clifftop height — but never the tide heights, which do not depend on where the observer stands. Defaults: from today, 2 days or the plan's limit if lower. Requires an API key on a paid Tides plan.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_tide_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC.
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees.
daysNoNumber of days to return. The ceiling is plan-dependent.
elevationNoMetres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zero. For irradiance it is height above sea level. Supply it when known: from a height the sun rises measurably earlier than the sea-level answer. Omit only if it is genuinely unknown.
start_dateNoFirst day as YYYY-MM-DD. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / elevation / description
      Previous value: -"Metres above sea level. Supply it when known: at altitude the sun rises measurably earlier than the sea-level answer. Omit only if the elevation is genuinely unknown."New value: +"Metres. For sun and moon times this is the observer's height above the horizon they look across: on a sea cliff or island peak, their height above sea level; on a plateau or in a valley, close to zero. For irradiance it is height above sea level. Supply it when known: from a height the sun rises measurably earlier than the sea-level answer. Omit only if it is genuinely unknown."
  2. Changed1 schema field changed
    • changedInput schema / properties / tz / description
      Previous value: -"IANA timezone for output timestamps, e.g. Europe/Dublin."New value: +"IANA timezone for output timestamps, e.g. Europe/Dublin. Defaults to UTC."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: an API key on a paid Tides plan is required, the default window is 'from today, 2 days or the plan's limit if lower', and elevation shifts sun/moon times but never tide heights. It does not discuss rate limits or failure modes, which keeps it short of a 5.

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?

The description is front-loaded with the return contents, then the routing rule, then the elevation caveat, then defaults and the auth requirement — a sensible priority order with no filler. It is dense but every sentence carries information; the only minor cost is that the elevation sentence packs several clauses together.

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?

There is no output schema, but the description enumerates the returned fields (tides, sun times, golden/blue hour, twilight, moon phase) and states the default date window, so an agent knows both what comes back and what happens if it omits optional parameters. The paid-plan requirement is the one operational prerequisite an agent could not infer from structured fields, and it is disclosed.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains the physical interpretation of elevation (observer height above the horizon looked across, roughly three minutes of shift at clifftop height) and clarifies that tide heights are unaffected. It also restates the start_date and days defaults, which the schema only partially covers.

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 opens with a specific verb-and-resource statement ('Per day: high and low waters together with sunrise, sunset, golden and blue hour, twilight and moon phase in a single call') and explicitly names the two sibling tools it replaces, so an agent can distinguish it from get_tide_extremes and get_sun_moon_times 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?

It states the intended audience and use case (coastal photography, fishing, shore work) and gives an explicit routing rule: 'use it instead of calling get_tide_extremes and get_sun_moon_times separately.' It also gives a conditional instruction for elevation ('Pass elevation when you know it... Omit only if it is genuinely unknown'), which is when-to-use guidance at the parameter level.

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.