Skip to main content
Glama

Automaty Neomezene CZ

online_hry

Read-only

Poskytuje přehled toho, co konkrétní stránka webu ukazuje o své hře, případně o seznamu her, podle adresy stránky.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAdresa stránky tohoto webu, celá nebo začínající lomítkem.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 the safety profile is covered by structured data. The description adds only that results are scoped to a given page address; it says nothing about fetch behavior, failure modes, caching, or what happens when the page contains no game data.

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 no filler; the page-address scoping is front-loaded. It is somewhat convoluted ('toho, co konkrétní stránka webu ukazuje o své hře, případně o seznamu her') but not wasteful.

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 no output schema present, the description carries the burden of explaining what the tool returns, yet it only says vaguely that it gives an 'overview' of games. For a single-parameter lookup tool that is otherwise simple, this leaves a meaningful gap about result shape and empty-result behavior.

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 url parameter is fully documented, including that it may be a full address or start with a slash. The description's phrase 'podle adresy stránky' merely restates this and adds no format or edge-case detail beyond the schema baseline.

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 names a verb ('Poskytuje přehled' – provides an overview) and a resource (game information on a web page, or a list of games), so the general function is discernible. However, 'what a specific page shows about its game' is vague about what is actually returned, and there is no explicit differentiation from siblings like hry_zdarma or jackpoty_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 guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. The only implied usage is that you supply a page address, which the schema already enforces via the required url field.

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