Skip to main content
Glama

najlepsze_jackpoty

Read-only

Zbiera opublikowane na witrynie zestawy gier o różnej tematyce. Do każdego zestawu dołączony jest adres jego strony. Liczba tematycznych kolekcji gier: 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": "najlepsze_jackpoty"
  }
}

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 by structured data. The description adds a small amount of behavioral context by saying each set comes with its page URL and that there is currently 1 collection, but it does not explain ordering, freshness, or what 'best' means. Useful but thin beyond the annotations.

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?

It is short and front-loaded with the main action, but the trailing sentence 'Liczba tematycznych kolekcji gier: 1' reads like a data artifact rather than guidance and its purpose is ambiguous. Little waste in wording, but the third sentence does not clearly earn its place.

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 tool with no output schema, the description should carry the burden of explaining what comes back; it does partially (sets plus their page URLs) but omits structure, count semantics, and jackpot-related content. Adequate to attempt a call, not complete enough to predict 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, which is the baseline-4 case since there is nothing for the description to disambiguate. The empty schema with additionalProperties=false matches the description's implication of a parameterless retrieval call.

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 verb and resource — collecting published themed game sets from the site, each with its page URL — but never mentions jackpots, so the link to the tool's own name ('najlepsze_jackpoty' / best jackpots) is unclear. It gives no hint of how this differs from siblings like jackpoty_szukaj or top_wygrane.

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 says when to pick this over jackpoty_szukaj or top_wygrane, and no preconditions or exclusions are stated. The agent must infer the use case purely from the tool name.

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