Skip to main content
Glama

jackpoty_zdarma

Read-only

Vrací obsah stránky webu podle její adresy: informace o hře, nebo seznam her.

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": "jackpoty_zdarma"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAdresa stránky v plném tvaru nebo od lomítka.

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?

The annotations already cover the key behavioral facts (readOnlyHint=true, openWorldHint=false), so the description is not required to establish safety. It adds only that the return value is either game information or a game list; it does not say whether the URL must belong to the specific site, what happens on an invalid or out-of-scope address, or whether responses are paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the verb first and the two outcome types trailing, with no filler. It is arguably too terse for its role, but nothing is wasted.

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?

With one fully documented parameter, read-only and closed-world annotations, and no output schema, the definition covers the minimum. What is missing is site-scoping information and any indication of what the returned 'content' looks like, which matters for an agent deciding whether to call it.

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 description coverage is 100%, and the URL parameter already documents that it accepts a full address or a path from the slash. The description restates that the input is a page address but adds no format or validation detail beyond the schema, so baseline 3 applies.

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 gives a concrete verb and resource ('Vrací obsah stránky webu podle její adresy') and names two possible payloads (game info or a game list). However, the name 'jackpoty_zdarma' (free jackpots) does not obviously match a generic page-content fetcher, and nothing distinguishes it from the siblings online_hry or vyhry_hledat.

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 statement of when to use this tool versus the alternatives, no prerequisite or exclusion conditions, and no mention of the sibling tools. The only implicit guidance is that a game or game-list result is expected, which an agent must infer.

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