Skip to main content
Glama

vyhry

Read-only

Vráti tematicky zamerané zbierky hier uverejnené na tomto webe. Ku každej z nich pripojí adresu príslušnej stránky. Zostavené tematické kolekcie: 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": "vyhry"
  }
}

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 one useful behavioral detail beyond that: the response includes the URL of each collection's page. It does not describe ordering, count, or what 'tematicky zamerané' means in practice.

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?

Two short sentences front-load the purpose, which is good, but the dangling 'Zostavené tematické kolekcie: 1' adds no intelligible information and reads like leftover template text. The core is lean, yet that fragment wastes the limited space and confuses scope.

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 read-only listing with no output schema, the description should at least characterize the return shape. It partially does by noting each collection comes with its page URL, but it leaves the collection structure, count, and the meaning of the trailing '1' unexplained, so an agent cannot fully anticipate the response.

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 and the schema is an empty closed object at 100% coverage, so no parameter explanation is required. Baseline 4 applies; the description correctly implies a no-argument full listing rather than a filtered query.

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 states a concrete verb and resource: it returns thematically focused game collections published on the site and appends each one's page address. However, it offers no differentiation from the siblings (automaty_hladanie, top_automaty), and the trailing fragment 'Zostavené tematické kolekcie: 1' is cryptic – it reads like a truncated or templated count rather than a stated scope.

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 tells the agent whether to prefer this over top_automaty or automaty_hladanie, and no conditions, prerequisites, or exclusions are given. The agent must infer the tool's role purely from the noun '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