Skip to main content
Glama

Rybárstvo.sk

Details of an accommodation or service listing

get_service
Read-onlyIdempotent

Full details of one listing from list_services (id): type, municipality and district, position, website, prices with units (e.g. per person per night), capacity (beds, extra beds, rooms), minimum stay, check-in and check-out, season and open months, room amenities and amenities for anglers, payment methods, spoken languages, owner-declared distance to the water, the nearest fishing waters measured to the shoreline or the water line (with typical fish), photos and a short summary in Slovak. Texts are supplied by the business owner; phone and e-mail are only on the listing page, where the enquiry form sends a message directly to the owner.

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

Input Schema

NameRequiredDescriptionDefault
idYesListing id from list_services.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new context — owner-supplied texts and the absence of direct contact details, with the enquiry form routing messages to the owner — but says nothing about behavior for an invalid or missing id, nor about response size or truncation.

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?

Front-loaded with the verb, resource and required id source before the field inventory. The long field enumeration is dense but justified because there is no output schema; the second sentence adds distinct value rather than padding.

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 usefully previews the returned content, including nested concepts like distance-to-water and per-unit pricing, so an agent knows what it will get. The main remaining gap is error/edge-case behavior for an unknown id.

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% and the single id parameter is already documented as 'Listing id from list_services'; the description only echoes that provenance. Baseline 3 applies since the schema carries the parameter semantics.

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 ('Full details of one listing') plus the source of the identifier ('from list_services') and enumerates the returned fields, which clearly separates it from the sibling list_services.

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?

Makes the usage path explicit: the id comes from list_services, so this is the follow-up detail call. It also warns that phone and e-mail are not returned here and that enquiries go through the listing page, which prevents a wrong-tool attempt. It stops short of naming any other alternative or stating when-not-to-use.

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