Skip to main content
Glama

top_vyhry

Read-only

Podľa adresy stránky vráti, čo táto webová lokalita zobrazuje – údaje o jej hre alebo zoznam hier.

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_vyhry"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesÚplná adresa stránky tohto webu alebo časť začínajúca lomítkom.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful behaviour that the response shape branches on the URL (single-game data vs a list of games), but says nothing about failure modes for malformed or off-site URLs or about the format of the returned 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 sentence, front-loaded with the URL condition and free of filler. It is efficient, though it spends its scarce space on a vague phrase ('čo táto webová lokalita zobrazuje') rather than on the tool's distinctive output.

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 no output schema, the description must convey return values, and it only sketches them ('game data or a list of games') without field-level detail or an example. Adequate to attempt a call, but thin for an agent that needs to know what it will get back.

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% (a single 'url' string with maxLength 300 and a note that it may be a path starting with '/'), so the schema carries the parameter burden. The description adds only marginal meaning by noting that the URL determines which kind of content 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 gives a specific verb ('vráti' – returns) and states the resource is the site's displayed content, split into 'údaje o jej hre' or 'zoznam hier'. However, it never ties back to the tool name 'top_vyhry' (top winnings/payouts), so the agent cannot tell whether payout data is actually returned, and no sibling is distinguished.

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?

Usage is only implied by the presence of a URL parameter ('Podľa adresy stránky'). There is no statement of when this tool is preferable to 'automaty' or 'hladat_hracie_automaty', no prerequisites, and no when-not 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