Skip to main content
Glama

Peskio

Fishing conditions for a day

conditions_get_day
Read-onlyIdempotent

One place, one day: fish activity score (bite) and best windows, go/marginal/no verdict per discipline (shore, boat, rock, kayak, spearfishing) with reasons, tide, sun, moon and solunar periods, wind and sea summary, water-clarity estimate, and how fresh the forecast is. Use for "is tomorrow good for…", "why is Saturday poor", "too rough today?", "water temperature now" (include hourly). Peskio has no current or slack-water data: never infer them from tide times. Thermocline and temperature at 5–30 m are in subsurface: a model estimate for some Mediterranean places in Spain and France, null elsewhere; when null, say Peskio does not have them and never infer them. Visibility at depth is unknown. Include a clickable link to the returned place.url with its query string unchanged. State the returned planning disclaimer when giving GO/marginal/NO; never assess whether a crossing, dive or trip is safe.

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": "conditions_get_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoLocal date at the place: YYYY-MM-DD, 'today', 'tomorrow' or an English weekday (the next one, today included); default today.
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
includeNo"hourly" for time-of-day or "right now" questions; "tideCurve" for a tide chart.
placeIdYesPeskio place id returned by places_search, e.g. "es:es-3108877". Never invent one.
audienceNoWho the answer is for.angler
disciplineNoOnly this discipline in decision.disciplines; default all five.

Output Schema

NameRequiredDescriptionDefault
sunYes
biteYes
dateYes
moonYes
tideYes
placeYes
hourlyNo
schemaYes
solunarYes
weatherYes
weekdayYesEnglish weekday of `date` (e.g. "Sunday"); use it, never compute weekdays yourself.
decisionYes
astroOnlyYesNo weather forecast for this day (beyond the ~14-day horizon, or not available): tide, sun and moon only.
freshnessYes
tideCurveNo
disclaimerYes
subsurfaceYesWater column at the place (thermocline, temperature at 5–30 m): a model estimate for some Mediterranean places in Spain and France; null elsewhere or when stale. When null, say it is unavailable. mixedLayerM follows the model's definition: density criterion as in de Boyer Montégut et al. (2004); thermoclineDeltaC is the drop across it, a measure of strength.
visibilityYes
attributionYes

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?

Beyond the read-only and idempotent annotations, the description discloses critical behavioral limits: no current or slack-water data, thermocline and 5–30 m temperatures are model estimates only for some Mediterranean places in Spain and France, visibility at depth is unknown, and nulls must not be inferred. It also states obligations to preserve the place.url query string, include the planning disclaimer for GO/marginal/NO verdicts, and never assess trip or dive safety.

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 dense but front-loads the returned data before moving into constraints and caveats. Most sentences carry necessary information, though the single-paragraph structure could be easier to scan given the number of behavioral rules.

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?

Given the tool's complexity, output schema, and complete parameter coverage, the description is complete enough for correct invocation. It covers data limitations, null-handling expectations, link preservation, disclaimer requirements, and safety-scope boundaries that an agent would not otherwise know.

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 100%, so every parameter is already documented in the input schema. The description reinforces the use of `include: ["hourly"]` for 'right now' questions and gives date examples, but it does not add substantial meaning beyond the schema baseline.

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 states a precise resource and scope: one place, one day, with the returned fishing activity score, discipline verdicts, tide, sun, moon, solunar periods, wind, sea, water clarity, and forecast freshness. The phrase 'One place, one day' implicitly separates it from multi-day comparison tools, and the listed outputs make the tool's purpose unmistakable.

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?

It gives concrete usage examples such as 'is tomorrow good for…', 'why is Saturday poor', 'too rough today?', and 'water temperature now' with the instruction to include hourly. It does not explicitly name alternative tools such as conditions_compare_days or tides_get_table, so the when-to-use guidance is clear but not fully rival-aware.

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