Skip to main content
Glama

top_wygrane

Read-only

Dla podanego adresu zwraca to, co dana strona witryny pokazuje: fakty dotyczące gry bądź listę gier.

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": {
      "url": "<url>"
    },
    "name": "top_wygrane"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAdres strony tej witryny: pełny lub zaczynający się od ukośnika.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description only says it returns page content, without disclosing the response shape, whether results are ranked, or how the two possible output kinds (facts vs. list) are distinguished. With no output schema this leaves a meaningful gap.

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 a single sentence with no filler, but it is front-loaded with a generic 'returns what the page shows' clause rather than the tool's actual purpose. Terseness here reflects under-specification rather than efficiency.

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 one simple parameter and no output schema, the description should carry the burden of explaining return values, yet it only vaguely gestures at 'facts about a game or a list of games.' An agent cannot predict what it will receive or how to interpret the two possible outcomes.

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 schema itself explains that the url is a full address or one starting with a slash. The description only restates 'for a given address' without adding format, validation, or scoping detail, so it lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns "what a given page of the site shows" – facts about a game or a list of games – but never ties this back to the tool name top_wygrane ('top wins'). It describes a generic page-fetch behavior rather than a specific verb+resource, leaving an agent unsure whether it produces rankings, game details, or arbitrary page content.

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 mention of the sibling tools (jackpoty_szukaj, najlepsze_jackpoty), and no exclusions. The description offers no signal about which of these tools to pick for a given task.

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