Skip to main content
Glama

Slots Oesterreich AT

walzen

Read-only

Abruf der Inhalte einer angegebenen Website-Seite: Angaben zu einem Spiel oder die Liste der Spiele.

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": "walzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDas Adressfeld akzeptiert die vollständige Adresse einer Seite oder den ab Schrägstrich beginnenden Teil.

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 declare readOnlyHint=true, so the description need not restate safety. It does add useful behavioral information by saying what the fetched page yields (single-game details vs. a game list), which is valuable since no output schema exists. It says nothing about failure behavior, response format (raw HTML vs. parsed), or the tension between fetching arbitrary pages and openWorldHint=false.

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?

One compact sentence, front-loaded with the operation and resource, with zero filler. It is efficient, though its brevity leaves the guidance and behavioral gaps noted above.

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 single-parameter read tool with annotations covering the safety profile and a fully documented parameter schema, the definition is adequate: it explains what is fetched and what kind of content comes back. It falls short on how results are returned and on error/edge behavior, which matters because no output schema exists.

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?

With a single parameter at 100% schema description coverage, the schema already explains that 'url' accepts a full page address or the slash-prefixed portion. The description adds no syntax, format, or constraint detail beyond that, so the baseline 3 applies.

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 specific verb (Abruf/retrieval) and resource (the contents of a specified website page), and even narrows the expected payload to either a single game's details or the list of games. This makes the opaque tool name 'walzen' interpretable. It does not, however, contrast itself with the siblings slots_finder or kostenlose_jackpots.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of the sibling tools that also deal with games. The only implicit hint is the stated payload ('Angaben zu einem Spiel oder die Liste der Spiele'), which suggests the tool is for fetching game data but leaves the choice between tools to inference.

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