Skip to main content
Glama

Peskio

Tide table

tides_get_table
Read-onlyIdempotent

Tide times, heights and Peskio coefficient estimates for one place over up to two weeks, with sunrise, sunset, daylight low tides and moon phase. Use for tide times, spring/neap tides, grandes marées, pêche à pied, tidal islands and boat launching. Heights are in metres above the stated datum. Information only: for tidal crossings, tell the user to follow the official crossing schedule. Peskio has no tidal-current or slack-water data: never derive them from these times. Explicitly label coefficients as Peskio estimates in the user language (French: estimation Peskio). Include a clickable link to place.url exactly as returned, query string included.

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": {
      "placeId": "<placeId>"
    },
    "name": "tides_get_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoAlias of `from` (the name the other Peskio tools use); `from` wins when both are given.
daysNo
fromNoFirst local date: YYYY-MM-DD, 'today', 'tomorrow' or an English weekday (the next one, today included); default today at the place.
langNoThe user's language (ISO 639-1; one of Peskio's 15, otherwise 'en'). Picks the peskio.com page language and local place names; answer in the user's language yourself.en
rankByNocoefficient = biggest first; low_tide = lowest low first; moon = closest to new/full moon first. Omit for date order.
placeIdYesPeskio place id returned by places_search, e.g. "es:es-3108877". Never invent one.
minCoefficientNoKeep only days whose Peskio coefficient is at least this. Grandes marées: 95. Pêche à pied: 70.
daylightLowOnlyNoKeep only days with a low tide in daylight.

Output Schema

NameRequiredDescriptionDefault
daysYes
datumYes
placeYes
rankByYes
regimeYes
schemaYes
sourceYes
windowYesThe local dates searched. When days is empty, say nothing matched IN THIS WINDOW and search the next one.
characterYes
datumNoteYes
disclaimerYes
attributionYes
filteredOutYes
heightsLabelYes
tideConfidenceYes
coefficientNoteYes
coefficientLabelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds behavior beyond that: heights are metres above the stated datum, coefficients are estimates that must be labeled as such in the user's language, no tidal-current data exists, and place.url must be echoed verbatim including the query string. These are non-obvious output-handling obligations an agent could not infer from structured fields.

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, then usage, then constraints and output obligations; every sentence carries information. It is dense and slightly long, with several imperative instructions in a row, but none are redundant filler.

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?

An output schema exists so return structure needn't be explained, and the description covers what remains: scope, datum, data limitations, labeling requirements, and verbatim link handling. Nothing an agent needs to call this correctly appears missing.

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 88%, so the schema already carries most parameter meaning (date/from aliasing, weekday aliases, rankBy, minCoefficient thresholds, daylightLowOnly). The description reinforces the two-week window and the datum of returned heights, but adds little about the individual parameters themselves; baseline 3 is appropriate.

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?

Opens with a specific verb-plus-resource statement: tide times, heights and Peskio coefficient estimates for one place over up to two weeks, and enumerates adjacent content (sunrise/sunset, daylight low tides, moon phase). The scope limits (one place, two weeks) let an agent separate this from the conditions_* and places_* siblings 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 explicit use cases (tide times, spring/neap tides, grandes marées, pêche à pied, tidal islands, boat launching) plus a clear when-not: never derive tidal currents or slack water from these times, and defer to official crossing schedules for crossings. It does not name a sibling tool as the alternative for the excluded current data, so it stops short of a full routing statement.

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