Skip to main content
Glama

Automaty Vyherne SK

online_jackpoty

Read-only

Prehľad tematických kolekcií hier tohto webu, ku každej s vlastnou adresou 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": "online_jackpoty"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 only a small behavioral hint that each collection carries its own page URL, and says nothing about ordering, count, or why the number "1" is appended.

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, but the second one is an unlabeled data fragment ("...: 1") that reads like truncated template output rather than a meaningful statement. The useful scope information is packed into the first sentence and the rest does not earn its place.

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

Completeness2/5

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

With no output schema, the description is the only place the return shape can be explained, and it only vaguely says each collection has a page address while leaving the "1" ambiguous. For a listing tool whose whole value is the returned structure, this is under-specified.

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 no parameters and the schema is closed with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter tool.

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 it returns an overview of this site's thematic game collections, each with its own page URL, which gives a rough verb+resource sense. However, the trailing fragment "Zostavené tematické kolekcie: 1" is unexplained and the description never distinguishes this listing tool from siblings like najst_jackpoty or top_sloty.

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, no exclusions, and no reference to alternatives such as najst_jackpoty or top_sloty. The agent must infer from the name alone that this is a browse-all-collections call.

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