Skip to main content
Glama

automaty

Read-only

Wykaz opublikowanych na witrynie kolekcji gier ułożonych według tematów, wraz z adresami stron. Kolekcje tematyczne: 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": "automaty"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 value by indicating the result includes page addresses (URLs) for each collection, which the annotations do not state. It does not clarify ordering, pagination, or the meaning of the '1' fragment, so it is useful but shallow.

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?

The body is a single short sentence, which is good, but the appended 'Kolekcje tematyczne: 1' is an unexplained fragment that adds noise rather than information. There is little front-loading problem, but the trailing token should have been omitted or expanded.

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 parameters and no output schema, the description carries the burden of explaining the return shape; it partially does so by mentioning page addresses. But an agent still cannot tell whether the result is a flat list, a single collection, or something keyed by theme. Adequate, with a clear gap.

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 and the schema is fully specified, so there is no parameter meaning to compensate for. The description correctly implies no input is required, matching the empty schema. Baseline 4 applies for a parameterless tool with no semantic gaps.

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 says it lists game collections published on the site, arranged by theme, with page addresses, so the resource and output are broadly identifiable. However, the trailing fragment 'Kolekcje tematyczne: 1' is cryptic and untied to the sentence, and nothing distinguishes this listing tool from the sibling tools darmowe_maszyny or szukaj_maszyny. Purpose is implied rather than crisply stated.

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 at all: no statement of when to prefer this over browsing free machines (darmowe_maszyny) or searching (szukaj_maszyny). The agent must infer the use case entirely from the noun 'collections'. No exclusions or prerequisites are offered.

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