Skip to main content
Glama

Rybárstvo.sk

Fish species and regulation

get_fish_species
Read-onlyIdempotent

Looks up a fish species by its name in any language of the site or its Latin name and returns what the Slovak decree says about it: year-round protection, minimum size, closed season, water types, plus the page URL. Informative only; always check the rules of the specific water.

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": {
      "name": "<name>"
    },
    "name": "get_fish_species"
  }
}

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.
nameYesSpecies name in Slovak, Latin or another supported language, e.g. "šťuka", "Esox lucius", "pike", "Hecht", "csuka", "щука", "pstruh potočný".

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 / name / description
      Previous value: -"Slovak or Latin species name, e.g. \"šťuka\", \"Esox lucius\", \"pstruh potočný\"."New value: +"Species name in Slovak, Latin or another supported language, e.g. \"šťuka\", \"Esox lucius\", \"pike\", \"Hecht\", \"csuka\", \"щука\", \"pstruh potočný\"."
  2. First observed

TDQS

A4.2/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, closed-world), so the description only needs to add context. It does so by disclosing the exact contents of the response and by flagging that the result is informative rather than authoritative, which is the key behavioral caveat for this tool.

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, front-loaded with the action and result payload, followed by the single most important caveat. No redundant or filler wording.

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 carries the burden of explaining return values and does so concretely. It stops just short of describing failure behavior, such as what is returned when a species name is not recognized, which is a minor gap for a two-parameter lookup tool.

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%, so both parameters are already documented, including the language enum and its fallback rule. The description reinforces that the name parameter accepts any site language or Latin name, but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (looks up) and resource (fish species by name in any supported language or Latin), then enumerates exactly what is returned: year-round protection, minimum size, closed season, water types, and page URL. This is enough for an agent to distinguish it from get_water or fishing_rules_today without opening a 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?

Gives clear usage context: it is informational and the agent should still defer to the rules of the specific water, which implies a different tool is authoritative for actual regulations. It does not name that alternative explicitly, leaving the routing inference to the agent.

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