Skip to main content
Glama

Automaty Vyherne SK

najst_jackpoty

Read-only

Funkcia vracia stránky hier, herných štúdií a kolekcií, ktorých názov obsahuje hľadaný výraz. Nezohľadňuje tému, motív ani popis. Recenzie hier: 20

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "najst_jackpoty"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesHľadaný výraz je názov hry, herného štúdia alebo kolekcie, prípadne časť takéhoto názvu, a obsahuje aspoň dva znaky.

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral constraint that matching is limited to titles and ignores theme, motif and description, plus an implication that results come back as paged listings. The trailing fragment 'Recenzie hier: 20' is opaque and adds no usable behavioral information, keeping this at an adequate-but-not-rich 3.

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 main sentence is front-loaded and waste-free, and the exclusion clause is placed sensibly. The final fragment 'Recenzie hier: 20' is unexplained and reads as leftover noise, which hurts structure without adding meaning.

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 one-parameter, read-only lookup with no output schema and full schema coverage, the description covers entity scope and matching rules adequately. It still omits pagination/result-limit behavior and never clarifies the 'jackpot' angle or the stray review count, so it is sufficient but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single q parameter is fully documented with min/max length in the schema. The description adds only marginal meaning beyond that, clarifying that q matches a full or partial name of a game, studio or collection. Baseline 3 applies since the schema carries the parameter burden.

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 concrete verb and resource set: it returns pages of games, game studios and collections whose name contains the search term. That is a clear, actionable statement of purpose. It loses a point because it never connects to the tool's own name (najst_jackpoty / 'find jackpots'), leaving the agent unsure how 'jackpot' filtering relates to the generic name search described.

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?

The negative scoping ('Nezohľadňuje tému, motív ani popis') usefully tells the agent this is a name-only search, which implies when it should be used. However, there is no positive guidance about when to prefer it over the sibling tools online_jackpoty or top_sloty, and no prerequisites or exclusions are named.

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