Skip to main content
Glama

Automaty Blik PL

automaty_online

Read-only

Przyjmuje adres jednej strony witryny. Zwraca to, co ta strona pokazuje: fakty o grze 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": "automaty_online"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPełny adres strony tej witryny albo część rozpoczynająca się od ukośnika.

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 safety and scope are covered structurally. The description adds one genuinely useful behavioral fact: the response shape depends on the page type (game facts vs. a game list). It says nothing about invalid URLs, unknown page types, or failure behavior.

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?

Two short sentences, front-loaded with the input then the output, with no filler. It is efficient, though the brevity is partly the cause of the missing guidance rather than a virtue of precision.

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 one parameter, a fully covered schema, and no output schema, the description needs to convey return shape and failure modes. It half-does the first (game facts or game list) and omits the second, leaving an agent unsure what happens on bad or unsupported URLs.

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% and the single url parameter is fully documented (full address or a path starting with a slash). The description only restates that it is a single page address, adding no format, domain, or normalization guidance beyond the schema.

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 states a specific action (przyjmuje adres jednej strony) and sketches the return ('fakty o grze albo listę gier'), so an agent knows this fetches a single page's content. However, it never says what kind of page/tool this is in relation to siblings like gry_online or szukanie_sloty, and 'to, co ta strona pokazuje' is a vague framing of a fetch operation.

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 when-to-use guidance, no exclusions, and no reference to any alternative tool. The phrase 'jednej strony' implies one page per call but doesn't tell the agent when this is preferable to the sibling tools.

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