Skip to main content
Glama

Rybárstvo.sk

Upcoming angling competitions

list_competitions
Read-onlyIdempotent

Upcoming angling competitions and events published on the portal (date, place, organiser, kind, page URL). Texts are supplied by the organisers.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOptional kind: kapor = carp, feeder = feeder/float, privlac = spinning, muska = fly fishing and catch & release, deti = children and youth, spolocenske = social event.
limitNoMaximum number of results (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's job is to add context beyond that — and it does, noting the fields returned and warning that texts come from organisers (i.e. unverified third-party content). It omits ordering/pagination behavior despite the limit cap, which keeps it short of a 5.

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 short sentences with the resource and scope front-loaded and the provenance caveat placed second. No redundant restatement of the title or schema, and every clause carries information.

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?

For a simple two-parameter, zero-required read tool with no output schema, the definition covers purpose, returned fields, and data reliability. The remaining gap is behavioral detail such as result ordering or what 'upcoming' means in terms of date range.

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 enum values for kind are fully documented in the schema, so the description need not re-explain them. It mentions 'kind' only as one of the returned fields, adding no filtering semantics beyond what the schema supplies.

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 (angling competitions and events) with a clear scope (upcoming, published on the portal) and enumerates the returned fields. It reads distinctly from siblings like list_articles or list_catches, though it does not explicitly contrast itself with any of them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as search_site or list_articles for broader portal content. The word 'upcoming' hints at the time scope but leaves the agent to infer it from the tool name and data alone.

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