Skip to main content
Glama

online_walzen

Read-only

Die Funktion listet die veröffentlichten thematischen Sammlungen von Spielen mit den zugehörigen Seitenadressen auf. Kuratierte Sammlungen: 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": "online_walzen"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already set readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that only *published* collections are returned, together with their page addresses, which is useful behavioral context, but it says nothing about ordering or about what an empty or partial result means.

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 main sentence is efficient and front-loaded, but the trailing fragment 'Kuratierte Sammlungen: 1' is cryptic: it is unclear whether it reports a count, labels a category, or is a truncation artifact. That sentence does not clearly earn its place, and it weakens an otherwise tight definition.

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 simple, parameterless, read-only list tool, the description covers the essentials: what it lists and that page addresses are included. However, because there is no output schema, the description should describe the shape of the result more clearly, and the ambiguous 'Kuratierte Sammlungen: 1' fragment leaves an agent unsure what it will receive.

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 accepts zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The schema is empty and fully consistent with the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource: it lists the published thematic game collections together with their page URLs. That is specific enough for an agent to understand the operation, but it does not distinguish the tool from the siblings beste_automaten or suchen_spielautomaten.

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?

It provides no guidance about when to use it, when to choose a different tool, or what preconditions apply. Although the siblings suggest narrower lookups exist, the description never mentions an alternative or a boundary.

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