Skip to main content
Glama

Automaty Neomezene CZ

hry_zdarma

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. Kurátorské výběry 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": "hry_zdarma"
  }
}

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 safety and locality are covered by structured data. The description contributes one useful behavioral detail — that the response includes a page address per collection — but says nothing about ordering, result count, or whether the list is fixed. That is adequate but thin given there is no output schema.

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 clause is compact and front-loaded, but the dangling 'Kurátorské výběry her: 1' fragment is unexplained and adds noise rather than information. The passive 'Seznamuje s' construction costs clarity where a direct verb would have sufficed.

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 no-parameter, read-only listing tool this is close to sufficient, and the note about per-collection URLs partially substitutes for the absent output schema. However, the shape and size of the returned collection list remain unspecified, and the trailing fragment leaves the scope ambiguous.

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 per the baseline there is nothing for the description to disambiguate. No parameter-related meaning is missing.

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 and gives each one's page address, which hints at a list-style read tool, but the verb 'Seznamuje s' (introduces/familiarizes with) is indirect rather than a concrete operation like 'lists'. The trailing fragment 'Kurátorské výběry her: 1' adds no discriminator and reads like a truncated artifact, so an agent cannot cleanly tell this apart from siblings such as online_hry.

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, when not to, or how it relates to the available alternatives (online_hry, jackpoty_hledat). The only usage signal is the implicit idea that this returns curated collections, which a caller must infer.

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