Skip to main content
Glama

Rybárstvo.sk

Fishing waters near a place

waters_near
Read-onlyIdempotent

Lists fishing waters (revíry) within a radius of a Slovak district town or of given coordinates, nearest first, with distance, water type, river, district and SRZ organisation. Give either city or both lat and lon.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in degrees (WGS84).
lonNoLongitude in degrees (WGS84).
cityNoName of a Slovak district town, also in other languages or historical form, e.g. "Nitra", "Žilina", "Košice", "Kaschau", "Kassa", "Кошиці".
langNoLanguage of the answer: texts and page URLs in this language. sk = Slovak (original), cs = Czech, en = English, de = German, pl = Polish, hu = Hungarian, uk = Ukrainian, es = Spanish, fr = French, ro = Romanian, it = Italian. Use the language of the user. If omitted, the language of the input is used when it can be recognised, otherwise Slovak.
limitNoMaximum number of results (default 10).
radius_kmNoSearch radius in kilometres (default 25).
water_typeNoOptional water type: carp = carp waters, trout = trout waters, grayling = grayling waters, other = other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Name of a Slovak district town, e.g. \"Nitra\", \"Žilina\", \"Košice\"."New value: +"Name of a Slovak district town, also in other languages or historical form, e.g. \"Nitra\", \"Žilina\", \"Košice\", \"Kaschau\", \"Kassa\", \"Кошиці\"."
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Language of the answer: texts and page URLs in this language. sk = Slovak (original), cs = Czech, en = English, de = German, pl = Polish, hu = Hungarian, uk = Ukrainian, es = Spanish, fr = French, ro = Romanian, it = Italian. Use the language of the user. If omitted, the language of the input is used when it can be recognised, otherwise Slovak.",
      +  "enum": [
      +    "sk",
      +    "cs",
      +    "en",
      +    "de",
      +    "pl",
      +    "hu",
      +    "uk",
      +    "es",
      +    "fr",
      +    "ro",
      +    "it"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/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 needs no restatement. The description adds real value by disclosing result ordering ('nearest first') and the fields carried in each result, but says nothing about truncation by limit or whether an empty radius yields an empty list.

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?

Two sentences, no filler: the first carries purpose, ordering and result fields; the second carries the input constraint. Structure is front-loaded with the core capability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully names the returned fields, which covers the biggest gap for a search tool. Still, for a 7-parameter geo-search it omits failure modes (unknown city, out-of-range coordinates) and does not describe how limit interacts with radius.

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?

The statement 'Give either city or both lat and lon' encodes an either/or constraint that the schema expresses only as all-optional properties, so it adds meaning beyond the 100% coverage baseline. The description does not elaborate on radius or water_type, but the schema handles those well on its own.

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 ('Lists fishing waters (revíry)') plus the retrieval basis (radius around a Slovak district town or coordinates), and enumerates the returned fields including distance and SRZ organisation. This clearly separates it from the single-record sibling get_water.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The closing sentence 'Give either city or both lat and lon' gives concrete invocation guidance on location input, which is genuinely useful. However, there is no guidance on when to prefer this over get_water or get_water_conditions, and no stated behavior when a city name is ambiguous or unmatched.

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