Skip to main content
Glama

Rybárstvo.sk

Get fishing water details

get_water
Read-onlyIdempotent

Details of one fishing water (revír), river/lake (tok) or river basin (povodie): code, water type, river, region and district, SRZ organisation, length, coordinates, key properties and page URL. Pass the numeric id from search_site/waters_near results, or the page url.

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

Input Schema

NameRequiredDescriptionDefault
idNoPage id of the water, as returned in the id field of other tools.
urlNoAlternatively, the full page URL of the water on this site.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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

A4/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 fully covered elsewhere. The description adds only the returned-field inventory and the fact that the answer adapts to lang; it says nothing about behavior when an id/url is unknown or whether both inputs may be combined.

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, zero filler, front-loaded with what the tool returns and followed by how to supply the identifier. The field list is dense but every item is a genuine return-value hint, which matters because no output schema exists.

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

Completeness4/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 compensates by enumerating the returned fields, and annotations cover the mutation/idempotency profile. The remaining gap is edge behavior — invalid id, missing record, or interaction between the id and url parameters — which is not addressed anywhere.

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% and the enum for lang is fully enumerated in-schema, so this is baseline territory. The description's only addition is the provenance of the id ('from search_site/waters_near results'), which the schema already implies with 'as returned in the id field of other tools'.

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 opens with a specific verb and resource ('Details of one fishing water (revír), river/lake (tok) or river basin (povodie)') and then enumerates exactly which fields come back (code, water type, region, district, SRZ organisation, length, coordinates, URL). An agent can distinguish this single-record lookup from the sibling list/search tools 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 Guidelines4/5

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

It tells the agent where the input comes from — 'Pass the numeric id from search_site/waters_near results, or the page url' — which is real routing guidance tying this tool to its siblings. It stops short of stating when not to use it (e.g. use get_water_conditions for current conditions instead), so it is clear context rather than a full decision rule.

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