Skip to main content
Glama

Peskio

Compare days at a place

conditions_compare_days
Read-onlyIdempotent

Rank up to 7 consecutive days at one place by fish activity score (bite, the default), verdict (overall or for one discipline) or water clarity, with tide coefficient, lowest low, moon and a wind/wave headline per day. Use for "best day to fish this weekend", "today or Thursday?", "clearest day this week". Name the days with dates and let the server resolve them: "this weekend" -> dates: ["weekend"]; "today or Thursday" -> dates: ["today", "thursday"]; or use from + days for a run of days. Days with no weather forecast (beyond the ~14-day horizon, or not available) are marked astroOnly and rank last for verdict and clarity. Include a clickable link to place.url exactly as returned, including the query string. GO/marginal/NO are conditions ratings for planning, not safety; say so. The fish activity score estimates fish activity, not abundance, and is not a discipline conditions score.

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_compare_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
fromNoFirst local date (YYYY-MM-DD or a day word); 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
datesNoSpecific days to compare, resolved at the place: YYYY-MM-DD, 'today', 'tomorrow', an English weekday (the next one, today included) or 'weekend' (the coming Saturday and Sunday; from today if it is Saturday, just today if Sunday). Overrides from/days.
rankByNobite
placeIdYesPeskio place id returned by places_search, e.g. "es:es-3108877". Never invent one.
audienceNoWho the answer is for.angler
disciplineNoFishing discipline: shore, boat, rock, kayak or spearfishing.

Output Schema

NameRequiredDescriptionDefault
daysYes
placeYes
rankByYes
schemaYes
disciplineYes
disclaimerYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context: days lacking a forecast are marked astroOnly and rank last for verdict and clarity, and the required clickable link to place.url including its query string. It does not cover pagination or error behavior, but this is well above what the annotations supply.

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?

Purpose is front-loaded in the first clause, then examples, then mechanics, then caveats -- a sensible order with no filler. It is on the long side, and the trailing disclaimers (GO/marginal/NO not safety, activity not abundance) are somewhat repetitive, but each carries a distinct correction.

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 eight parameters, an output schema and existing annotations, the description covers everything an agent needs: what it returns per day, how dates resolve, how astroOnly days rank, and the required link format. Return-value detail is redundant against the output schema but harmless, and no decision-relevant gap remains.

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 75% and the description meaningfully extends it -- it spells out the 'weekend' and 'today/thursday' date-word forms with literal examples, explains that from + days builds a run of days, and clarifies rankBy's three modes including that verdict can be overall or discipline-specific. The lang, audience and placeId parameters are left to the schema, but the ambiguous ones are handled.

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 concrete verb and resource -- rank days at one place by fish activity score, verdict or water clarity -- plus the hard scope limit (up to 7 consecutive days) and the per-day payload. An agent can immediately tell this is a multi-day comparison tool rather than a single-day lookup.

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 three concrete user-intent examples ("best day to fish this weekend", "today or Thursday?", "clearest day this week") and explains the two ways to specify days (named dates vs. from + days). It stops short of naming a sibling to use for a single day instead, so the when-not-to-use case must be inferred from the 7-day framing.

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