Skip to main content
Glama

top_automaty

Read-only

Wynik zależy od adresu strony: pokazuje to, co witryna umieściła na wskazanej podstronie — opis gry albo listę gier.

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

Input Schema

NameRequiredDescriptionDefault
urlYesStrona tej witryny jest wskazywana pełnym adresem albo fragmentem zaczynającym się od ukośnika.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 and scope are covered. The description adds one genuinely new behavioral fact — that the returned payload varies by page type (a game description versus a game list) — but says nothing about whether the page is fetched live, error behavior for invalid addresses, or shape of the result.

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, front-loaded sentence with no filler or repetition. It is efficiently written, though the brevity comes partly at the cost of specificity.

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?

There is no output schema and no annotation describing the return value, so the description carries the burden of explaining what comes back; it gestures at two possible payload types but not their structure. For a tool whose result is entirely determined by the input URL, the lack of any guidance on valid page forms or failure cases leaves significant gaps.

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 parameter already documents that the address may be a full URL or a slash-prefixed fragment. The description's mention of 'adres strony' adds no syntax or constraint beyond that, so the baseline of 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 names a resource (content of a subpage of 'this site') and says it returns either a game description or a game list, but the verb is only 'shows' and the tool name (top_automaty, implying a ranking of slots) is not reconciled with the described page-fetch behavior. An agent can guess it retrieves page content, but cannot confidently tell what distinguishes it from maszyny_online or znajdz_sloty.

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?

The description states only that results depend on the URL; it gives no condition for choosing this tool over the sibling tools, no exclusions, and no prerequisites. Usage must be inferred entirely from the URL parameter.

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