Skip to main content
Glama

vyherni_automaty

Read-only

Vrací seznam tematických kolekcí her zveřejněných na tomto webu spolu s adresami příslušných stránek. Sbírky her podle témat: 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": "vyherni_automaty"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a read-only, non-open-world operation, so the safety profile is covered. The description adds that results include the URL of each collection page, which is useful because there is no output schema, but it says nothing about ordering, pagination, or result size.

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 compact and front-loaded with the main action. The trailing fragment 'Sbírky her podle témat: 1' is garbled filler that carries no usable meaning and should not be there.

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 zero-parameter read tool with no output schema, the description adequately conveys what comes back (a list of thematic collections with their page URLs) and asks for no inputs. Only the absence of any ordering or sizing hint keeps it short of full completeness.

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 input schema is an empty object, so there are no parameters to explain and the baseline of 4 applies. Nothing in the description contradicts or misrepresents the zero-argument signature.

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 gives a specific verb and resource in Czech: 'Vrací seznam tematických kolekcí her' (returns a list of thematic game collections) plus the fact that each entry carries its page address. That is enough for an agent to tell it apart from a search tool like hledat_vyhry, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the description says the tool returns thematic collections, which hints at browsing rather than searching, but it never states when to prefer it over hledat_vyhry or hry_zdarma, and offers no exclusions or prerequisites.

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