Skip to main content
Glama

Rybárstvo.sk

Local SRZ organisation and its waters

get_srz_organisation
Read-onlyIdempotent

A local or town organisation of the Slovak Anglers' Union (MO/MsO SRZ) by name: registered address, website, portal page and the fishing waters it manages (with ids for get_water). Personal contacts of officials are not provided.

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_srz_organisation"
  }
}

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.
nameYesOrganisation or town name (town also in other languages), e.g. "Piešťany", "MO SRZ Žilina", "Bratislava 1", "Pressburg".
limitNoMaximum number of waters listed (default 30).

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: -"Organisation or town name, e.g. \"Piešťany\", \"MO SRZ Žilina\", \"Bratislava 1\"."New value: +"Organisation or town name (town also in other languages), e.g. \"Piešťany\", \"MO SRZ Žilina\", \"Bratislava 1\", \"Pressburg\"."
  2. First observed

TDQS

A3.9/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 safety profile is covered. The description adds value beyond them: it enumerates what the response contains, explicitly states that officials' personal contacts are withheld (a privacy boundary an agent would otherwise probe for), and identifies the ids as inputs for get_water. It does not describe not-found or multi-match behavior.

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?

A single front-loaded sentence with a colon-delimited payload list, no filler, and the negative constraint placed last. It is dense but readable; the parenthetical '(with ids for get_water)' efficiently conveys both an output field and its downstream use.

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 telling the agent what comes back, and it does so field-by-field, plus it warns about the withheld contact data. Remaining gaps — behavior on unknown or duplicate names, and how limit interacts with the water list — are modest but real for a 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% and each parameter is thoroughly documented in the schema itself, including the full language enum, fallback behavior, and the limit range/default. The description adds no parameter-level detail beyond what the schema already supplies, so the baseline of 3 applies.

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 specific resource (a local/town organisation of the Slovak Anglers' Union, MO/MsO SRZ), the lookup key ('by name'), and enumerates the returned fields: registered address, website, portal page and managed waters. It also distinguishes itself from the sibling get_water by explaining that water ids are provided as handoff keys. The verb is implicit in 'by name' rather than stated, which keeps it just short of a 5.

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 establishes a clear workflow: resolve the organisation by name, then feed the returned water ids into get_water. It also flags an explicit scope exclusion (personal contacts of officials are not provided), which prevents a wasted call for that data. It does not address what to do when the name is ambiguous or unknown, nor point to search_site as a fallback, so no explicit when-not guidance.

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