Skip to main content
Glama

top_jackpoty

Read-only

Zwraca tematyczne kolekcje gier opublikowanych na tej witrynie wraz z adresami ich stron. Kolekcje tematyczne: 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": "top_jackpoty"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 one useful behavioral detail, namely that results include the collection page addresses, but since there is no output schema, it does not describe the shape of a collection entry or how many collections are returned.

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 core sentence is efficient and front-loaded, but the dangling enumeration 'Kolekcje tematyczne: 1' looks like a truncated list rather than meaningful content. It consumes space without informing the agent what the available collections are.

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 simple, parameterless read tool this is close to adequate: the agent knows it returns curated collections with URLs. However, the truncated collection list leaves the scope of returned data unclear, and with no output schema the description could say more about the result structure.

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, so there is no parameter semantics for the description to explain. That absence is correctly reflected by the baseline score of 4.

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: it returns thematic collections of games published on the site, along with the URLs of their pages. That is enough to distinguish it from siblings like nowe_wygrane and sloty_szukaj. The trailing fragment 'Kolekcje tematyczne: 1' is incomplete and adds no discriminating information.

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?

No guidance is given about when to use this tool instead of nowe_wygrane or sloty_szukaj, nor about prerequisites or expected call frequency. The agent must infer the use case (browsing curated categories) purely from the purpose sentence.

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