Skip to main content
Glama

online_hry

Read-only

Vrací seznam tematických kolekcí her zveřejněných na tomto webu spolu s adresami příslušných stránek. Tematické kolekce her: 1

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description does add that the response includes page addresses for each collection, which is useful return-content context not present in the schema. It says nothing about ordering, pagination, or whether the single collection noted is the entire return set. There is no contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well-formed and front-loaded with the verb and resource. The trailing fragment 'Tematické kolekce her: 1' is an incomplete, unexplained artifact that neither structures nor clarifies the definition. Two sentences total, one of which does no work.

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 zero-parameter read-only list tool with annotations covering the safety profile and no output schema, the description covers what is returned and in what form. Minor gaps remain around result ordering and the meaning of the trailing '1', but nothing essential to invoking it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the no-parameter baseline applies. The stray '1' at the end is not a parameter explanation and cannot be interpreted as one. Nothing about argument meaning is missing because arguments do not exist.

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?

States a specific verb and resource: returns the list of thematic game collections published on the site, together with the URLs of their pages. That is enough to tell it apart from the result-oriented siblings hry_vysledky and online_vyhry, though the description never names the alternatives explicitly. The dangling trailing fragment 'Tematické kolekce her: 1' adds no information and slightly muddies the purpose.

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 when-to-use guidance at all: nothing about when to pick this over hry_vysledky or online_vyhry, and no stated preconditions. The only implied use is discovering the site's collection pages, which an agent must infer from the purpose statement. No exclusions or alternatives are given.

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