Skip to main content
Glama

beste_automaten

Read-only

Zeigt anhand der Seitenadresse, was eine Seite dieser Website darstellt, also die Daten eines Spiels oder die Übersicht 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": "beste_automaten"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesZulässige Seitenadresse: vollständige Adresse der Seite oder mit Schrägstrich beginnender Teil.

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 closed-world scope are covered. The description adds that the result depends purely on the URL (a page-type determination rather than a live fetch), but says nothing about failure behavior for invalid or off-site URLs, nor how the determination is made.

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 with the input condition ('anhand der Seitenadresse') front-loaded. The trailing 'also die Daten eines Spiels oder die Übersicht der Spiele' is a useful concrete elaboration, though the circumlocution 'was eine Seite ... darstellt' could be stated more directly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of explaining what comes back, and it only vaguely gestures at 'die Daten eines Spiels oder die Übersicht der Spiele'. An agent cannot tell whether it receives a type discriminator, a redirect target, or actual game records — a significant gap for a tool whose entire value is its return value.

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 coverage is 100% and the single 'url' parameter is fully documented in the schema itself, including accepted full or slash-prefixed forms. The description's 'anhand der Seitenadresse' only restates that the URL is the input, adding no format or constraint detail beyond the schema — baseline 3 applies.

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 function (resolve a page URL to what that page represents — a single game's data or the games overview), which is more specific than the name 'beste_automaten'. However, the phrasing 'was eine Seite dieser Website darstellt' is indirect and never plainly says it classifies or describes a page, and it does not differentiate the tool from siblings like suchen_spielautomaten or online_walzen.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by 'anhand der Seitenadresse' — an agent can infer it should call this when it holds a page URL. There is no explicit when-to-use, no when-not-to-use, and no mention of the sibling tools as alternatives for searching or fetching machine data.

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