Skip to main content
Glama

automaty

Read-only

Zoznam tematických kolekcií hier publikovaných na tomto webe s uvedením adresy stránky pri každej z nich. Počet kolekcií: 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": "automaty"
  }
}

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?

Annotations already declare this to be a safe read (readOnlyHint=true) with no external calls (openWorldHint=false). The description adds a genuine behavioral detail, 'Počet kolekcií: 1', telling the agent how large the result set is, plus the fact that each entry carries a URL. Beyond that it says nothing about ordering, pagination, or result format.

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

Conciseness4/5

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

Two short sentences, front-loaded with what the tool returns and followed by the collection count. Nothing is padded. The hardcoded count is the only questionable element, since a static number of collections in a description can go stale as the site grows.

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 parameterless read-only listing tool with no output schema, the description covers what the result is at a high level, so an agent could call it correctly. It remains incomplete on the return shape, such as whether collections are ordered or paginated, and the static count may not reflect reality.

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 a closed empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter-level detail is needed.

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: it lists thematic game collections published on this site, with the page URL for each. That is far more informative than a restatement of the name 'automaty'. It does not, however, contrast itself with the sibling search tool hladat_hracie_automaty, so the distinction is left to the agent.

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?

The description contains no when-to-use guidance and no exclusion of alternatives. An agent reading it cannot tell whether to call this or hladat_hracie_automaty when looking for a specific game, and there is no mention of prerequisites or context of use.

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