Skip to main content
Glama

online_vyhry

Read-only

Na vstupu přijímá adresu stránky tohoto webu a na výstupu podává informace o její hře nebo její 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": "online_vyhry"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPole přijímá úplnou adresu stránky i část začínající lomítkem.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 genuinely useful constraint beyond them: the URL must be a page 'of this website', limiting scope. It says nothing about what happens with an invalid or non-site URL, nor about the ambiguity that the same call can return either a single game or a list.

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?

A single sentence with no filler, but it is structured as a circular 'on input X, on output Y' frame that spends words restating the obvious. The most decision-relevant fact, the URL-type-to-output-shape relation, is absent rather than front-loaded.

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, the description carries the burden of explaining the return value, and it does so only vaguely ('its game or its list of games') without saying how an agent knows which one it will get. For a tool whose behavior apparently branches on the supplied URL, this leaves a meaningful gap.

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 single `url` parameter is fully described, including that a bare slash-leading path is accepted, so the baseline is 3. The description adds only the domain restriction ('pages of this website'), and does not clarify that the URL type (game page vs. listing page) appears to determine which of the two output shapes comes back.

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 specific input (a page URL on this site) and output (information about its game, or a list of games), so the mechanics are stated. But 'online_vyhry' is never connected to a concrete resource — it does not say what a 'vyhra' is — and the output described ('information about its game or a list of games') reads almost identically to what a sibling like online_hry would do, so no sibling differentiation is achieved.

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 when-to-use or when-not-to-use guidance is provided, and the two sibling tools are not mentioned or routed to. The only implicit guidance is that a URL from this website is expected, which is a precondition rather than usage guidance.

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