Skip to main content
Glama

online_hry

Read-only

Seznamuje s tematickými kolekcemi her uvedenými na tomto webu a u každé z nich uvádí adresu její stránky. 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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a useful signal about the response contents (each collection comes with its page URL), but says nothing about ordering, count, or what 'Tematické kolekce her: 1' means.

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 core sentence is reasonably tight, but the trailing 'Tematické kolekce her: 1' is an unexplained fragment that reads like a truncation artifact and wastes the front-loaded advantage. Structure would be fine if that tail were removed or clarified.

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

Completeness3/5

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

For a zero-parameter, no-output-schema tool the description should more fully convey what comes back; it does mention collection names plus page URLs, which is the key return detail, but the odd numeric tail and lack of any usage context leave it short of complete.

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 the schema carries no semantic burden and the baseline of 4 applies. The description correctly implies a no-argument, list-everything retrieval.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it presents thematic game collections on this site and gives each collection's page URL, which conveys the resource, but the verb 'seznamuje' (introduces/familiarizes) is vague about the actual operation, and there is no differentiation from the siblings jackpoty_zdarma or vyhry_hledat. The dangling fragment 'Tematické kolekce her: 1' adds no clarity.

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 statement of when to use this tool rather than a sibling, no prerequisites, and no exclusions. An agent must infer the use case purely from the phrase about thematic collections.

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