Skip to main content
Glama

Rybárstvo.sk

Closed seasons and fishing hours today

fishing_rules_today
Read-onlyIdempotent

What the Slovak fishing act and decree say for a given day: whether all fishing is closed on trout, grayling and carp waters, the legal daily fishing hours, and which species are in their protection period. With water_id it also says which water types apply to that water. National rules only; the water's own angling rules can be stricter.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date YYYY-MM-DD (default today, Europe/Bratislava).
water_idNoOptional page id of a fishing water.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description's job is scope, which it does well: Slovak national law only, local angling rules may override, and water-type applicability requires water_id. It does not state what happens with an invalid water_id or an out-of-range date, but the substantive behavioral context is present.

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 sentences with no filler; the core purpose is front-loaded and the scope caveat is placed at the end where it functions as a qualifier. The first sentence is dense with a three-part list but nothing is redundant.

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?

No output schema exists, and the description compensates by enumerating the substantive return contents (closure status, hours, protected species, water types). Only edge-case behavior (invalid water_id, dates outside the decree's year) is left unstated, which is a minor gap for a two-parameter read 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 coverage is 100%, so both parameters are already documented, and the description only lightly adds meaning (that water_id extends the answer to water types). The date parameter's default and timezone are already in the schema description, so there is little added semantics beyond baseline.

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?

Names the specific resource (Slovak fishing act and decree rules for a given day) and enumerates the concrete answers it produces: closures on trout/grayling/carp waters, legal daily fishing hours, and species in protection period. This is clearly separable from siblings like get_water or get_water_conditions, which supply water data rather than legal rules.

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?

Implies the use case (a date-specific legality check) and explains the conditional add-on: with water_id it also reports which water types apply. The caveat 'National rules only; the water's own angling rules can be stricter' sets a clear scope boundary, though no alternative tool is named for water-specific rules.

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