Skip to main content
Glama

Automaty Blik PL

gry_online

Read-only

Nazwy tematycznych kolekcji gier z tej witryny oraz adresy ich stron. Kolekcje według motywów: 1

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gry_online"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. The description usefully adds what the payload contains (collection names and their page addresses), which matters since no output schema exists. It stops short of noting ordering, completeness of the collection list, or how the URLs should be followed.

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

Conciseness2/5

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

The body is short, but it is not clean: the second sentence ends mid-thought with a bare '1', which reads as a truncated enumeration rather than intentional content. An agent gains no signal from that fragment and may misread it as a parameter or count.

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?

For a zero-parameter, read-only listing tool with no output schema, the description does cover the essentials — it names what is returned (collection names and page URLs). But the truncated theme enumeration leaves the shape of the result (how many collections, how themes map to them) unclear, and there is no hint about how to chain into the sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics for the description to compensate for. Nothing in the description misrepresents the input surface.

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 identifies the resource — thematic game collections from the site — and states that it returns their names plus page URLs. However, the verb is only implied (a noun phrase rather than 'list/return'), and the trailing fragment 'Kolekcje według motywów: 1' is truncated and adds no discernible scope. It does not differentiate itself from siblings automaty_online or szukanie_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?

There is no when-to-use guidance: nothing says whether this is for browsing categories versus searching individual games, nor when an agent should prefer szukanie_sloty or automaty_online. The dangling 'motywów: 1' fragment hints at a thematic breakdown but never states a usable selection rule.

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