Skip to main content
Glama

Supersurf

Get tide times

get_tide_times
Read-onlyIdempotent

Use this when the person asks about the tide at a spot. Not for waves or wind: use get_surf_forecast. Answers a spot's high and low tides for the coming days (at most 14) in its own time zone, with heights, worked out from the tide constants of the nearest station; says so where there is none.

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": {
      "spot": "<spot>"
    },
    "name": "get_tide_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
spotYesa surf spot's id as search_surf_spots or list_surf_spots_near show it, or its name (Ericeira, Supertubos, Hossegor)

Output Schema

NameRequiredDescriptionDefault
spotYes
tidesYes
stationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations the description discloses real behavioral traits: the 14-day cap, that results are returned in the spot's own time zone, that heights are derived from the nearest station's tide constants, and that the output says so when no station exists. That provenance and edge-case handling 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.

Conciseness5/5

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

Three short sentences, front-loaded with the use case, then the exclusion, then the capability detail. Every clause carries information and none repeats the title.

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?

With an output schema present the description needn't enumerate return fields, yet it sketches them (heights, time zone, station basis) anyway. Combined with the sibling routing and the no-station caveat, an agent has everything needed to call this correctly.

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 50%, with only 'spot' documented in the schema; the description compensates partly by restating the 14-day ceiling on 'days' and by describing the output shape tied to that window. It does not state the default for 'days' or what happens below 1, so a gap remains, but the prose adds meaning beyond the partial 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?

The description uses a specific verb and resource ('answers a spot's high and low tides for the coming days') and immediately distinguishes the tool from get_surf_forecast by ruling out waves and wind. An agent can identify the resource and its scope 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 Guidelines5/5

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

It states the triggering condition ('when the person asks about the tide at a spot') and an explicit exclusion with the correct alternative ('Not for waves or wind: use get_surf_forecast'). Nothing about selection is left to inference.

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