Skip to main content
Glama

Peskio

Best spots nearby

spots_find_best
Read-onlyIdempotent

Rank up to 10 places within 5-25 km of a centre place for one day, on a given local hour or on each place's best daylight hour, by fish activity score (bite), verdict or water clarity. Use for "where near X is best tomorrow", "best spot at 7 am", "clearest water near Y". For "near me" omit placeId; if that fails, ask the user for a town or beach name. For regions wider than 25 km call it at several named centres. Link every recommended spot using its returned url exactly, query string included. Returned place names can be ambiguous across regions. Exact coordinates are unavailable in these ranked results. GO/marginal/NO are conditions ratings for planning, not safety; say so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spots_find_best"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoLocal date at the place: YYYY-MM-DD, or 'today', 'tomorrow' or an English weekday ('saturday' = the next one, today included). Prefer the words over computing dates yourself.
hourNoLocal hour 0-23 to rank on; omit for each place's best daylight hour.
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
limitNo
rankByNobite
placeIdNoCentre place from places_search. Omit only for "near me" questions.
audienceNoWho the answer is for.angler
radiusKmNo
disciplineNoFishing discipline: shore, boat, rock, kayak or spearfishing.

Output Schema

NameRequiredDescriptionDefault
dateYes
hourYes
noteYes
spotsYes
centreYes
rankByYes
schemaYes
omittedYesCandidate cells not evaluated, because the response-time budget was spent or a single place could not be evaluated; same-cell neighbours de-duplicated before candidate selection are never counted here.
weekdayYesEnglish weekday of `date` (e.g. "Sunday"); use it, never compute weekdays yourself.
radiusKmYes
timezoneYes
astroOnlyYesTrue when no ranked spot has a weather forecast.
consideredYes
disciplineYes
disclaimerYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), and the description adds genuinely non-obvious traits: ranked results carry no exact coordinates, place names can collide across regions, returned urls must be linked verbatim with query string, and GO/marginal/NO are planning ratings rather than safety advice. The one gap is no mention of result cardinality behavior when fewer than `limit` places fall inside the radius.

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 the core capability, then constrained to short imperative clauses with no filler. It is dense and does mix output-handling rules into the definition, but every sentence (url linking, name ambiguity, no coordinates, ratings-not-safety) carries information an agent would otherwise get wrong.

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?

For a 9-parameter, open-ended spatial ranker with an output schema, the definition covers the search-window limits, the near-me failure path, wide-region chunking, name ambiguity, absent coordinates, and the safety disclaimer on ratings. Nothing an agent needs to invoke or report correctly is missing.

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 67% and the description still adds practical meaning: it fixes the radius window (5-25 km), explains that omitting `hour` ranks on each place's best daylight hour, ties `placeId` to places_search and the 'near me' exception, and frames `date` as a single day. `lang`, `audience` and `discipline` get no mention, but their enum values are largely self-explanatory.

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 specific verb and resource with full scope: 'Rank up to 10 places within 5-25 km of a centre place for one day', plus the three ranking dimensions (bite, verdict, water clarity). An agent can immediately distinguish this from places_search (lookup) and conditions_get_day (single-day conditions) 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?

Gives concrete query shapes it serves ('where near X is best tomorrow', 'best spot at 7 am', 'clearest water near Y'), an explicit fallback path for 'near me' failures (ask for a town or beach name), and a workaround for oversized regions (call at several named centres). This is when-to-use plus how-to-recover guidance rather than a bare capability 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