Skip to main content
Glama

hry_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": "hry_zdarma"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesStránka webu určená celou adresou, případně částí od lomítka.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety is covered. The description adds that the response is either game detail or a game list, but says nothing about failure modes for unknown URLs, domain restrictions implied by openWorldHint=false, or rate limits.

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

Conciseness5/5

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

One sentence, front-loaded with the action and immediately followed by the two possible content outcomes. No filler or redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description usefully discloses the two return shapes (game info vs. list of games). For a one-parameter read tool this is nearly sufficient, though the response structure and error behavior remain unspecified.

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?

With a single parameter at 100% schema coverage, the schema already documents that the URL may be a full address or a path fragment from the slash. The description's 'podle její adresy' merely restates this and adds no new format or validation meaning.

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 specific verb and resource ('Vrací obsah stránky webu podle její adresy') and narrows the payload to 'informace o hře, nebo seznam her', which lets an agent distinguish a page-fetch from search-style siblings. It stops short of explicitly naming how it differs from hledat_vyhry or vyherni_automaty.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: call it when you have a page address and need that page's content. There is no explicit statement of when to prefer it over the sibling tools, nor any precondition such as needing a URL from the target site first.

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