Skip to main content
Glama

Rybárstvo.sk

Accommodation, shops and services for anglers

list_services
Read-onlyIdempotent

Businesses listed in the portal catalogue near a fishing water or place: accommodation, restaurants, fishing tackle shops, e-shops (by region), guides and boat rental, and fish sales. Returns name, type, distance, district, starting price, opening hours text, website and page URL; phone and e-mail are only on the listing page. Texts are supplied by the business owners. Give water_id, city, or 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": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in degrees (WGS84).
lonNoLongitude in degrees (WGS84).
cityNoName of a Slovak district town, e.g. "Piešťany".
kindNoOptional type: ubytovanie = accommodation, restauracia = restaurant, predajna = tackle shop, eshop = online shop, sluzba = guide/course/boat rental/service, ryby = fish sales.
limitNoMaximum number of results (default 10).
water_idNoPage id of a fishing water (from search_site or waters_near); its position is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds real context beyond them. It discloses the exact result fields, flags that phone and e-mail exist only on the listing page (a data-availability limit that changes agent expectations), and warns that texts are owner-supplied (data-quality caveat). It stops short of stating result ordering or pagination behaviour.

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?

Purpose is front-loaded in the first clause, and the long middle sentence listing return fields is justified because there is no output schema. It is dense and slightly run-on, packing category list, return fields, and caveats into three sentences, but no sentence is filler.

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

Completeness5/5

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

With six optional parameters and no output schema, the description carries its weight: it names the kinds, enumerates return values, explains the three locator inputs, and adds data-quality caveats. The only residual gap — no statement of result ordering or behaviour when called with no locator — is minor for a read-only listing 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%, including the kind enum and lat/lon bounds, so the baseline is 3. The description does add one useful signal — that a location can be expressed via water_id, city, or lat/lon — and hints e-shops are found 'by region', but it never says whether these locators are mutually exclusive, which takes precedence, or what happens when none is given.

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 ('Businesses listed in the portal catalogue') and immediately enumerates the six underlying kinds (accommodation, restaurants, tackle shops, e-shops, guides/boat rental, fish sales). That enumeration matches the 'kind' enum and makes the tool unmistakable against siblings like list_articles, list_catches or waters_near.

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?

Usage is implied by 'near a fishing water or place' and the closing 'Give water_id, city, or lat and lon', which tells the agent what input to supply but not when to prefer this tool over a sibling. There are no explicit exclusions or named alternatives, so the agent must infer that this is the business-directory counterpart to the water/catch listing tools.

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