Skip to main content
Glama

Rybárstvo.sk

Recorded catches and records

list_catches
Read-onlyIdempotent

Catches recorded by anglers on the portal (species, length, weight, date, water, whether released, angler's public name, page URL), optionally for one water or river and one species, ordered by length, weight or date. Exact catch spots are never returned. Entries are supplied by anglers.

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

Input Schema

NameRequiredDescriptionDefault
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).
orderNolength = longest first (default), weight = heaviest first, recent = newest first.length
speciesNoOptional species name in any supported language or Latin, e.g. "kapor", "carp", "Sander lucioperca".
water_idNoOptional page id of a fishing water, river or basin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
      +}
    • changedInput schema / properties / species / description
      Previous value: -"Optional Slovak or Latin species name, e.g. \"kapor\", \"Sander lucioperca\"."New value: +"Optional species name in any supported language or Latin, e.g. \"kapor\", \"carp\", \"Sander lucioperca\"."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context: 'Exact catch spots are never returned' (a privacy constraint that affects how results can be used) and 'Entries are supplied by anglers' (provenance/reliability caveat). It does not describe pagination or behavior for empty result sets.

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?

Two front-loaded sentences with no filler, and the field list is packed into a single parenthetical rather than spread across bullets. Slightly dense but appropriately sized for a five-parameter list tool.

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?

There is no output schema, so enumerating the returned fields is necessary and done well, and the privacy note covers a key edge case. Gaps remain around pagination (limit only, no offset) and result-set behavior when filters match nothing, which matter for an agent planning repeat calls.

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 coverage is 100%, so every parameter is already documented with enums and defaults; baseline is 3. The description only restates that results can be filtered by water/river and species and ordered by length, weight, or date, adding no semantics beyond the schema (and 'date' loosely maps to the enum value 'recent').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ('Catches recorded by anglers on the portal') and enumerates the returned attributes, so an agent knows exactly what comes back. It does not contrast itself with any sibling, but its subject (catch records) is distinct from the article/competition/water tools in the catalog.

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 description implies usage through the optional 'one water or river and one species' filtering and the ordering choices, which tells the agent how to narrow results. It never states when this tool should be preferred over another (e.g., get_water for water details), so guidance is implicit rather than explicit.

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