Skip to main content
Glama

Crashgames Casino AT

spiele

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

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scoping context by saying it returns page content about a game or the game list, but it says nothing about failure behavior, invalid or partial URLs, or how large a page response can be.

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 front-loaded sentence with a colon that separates action from payload; nothing is redundant. It is appropriately short for a one-parameter read tool.

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

Completeness4/5

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

For a single-parameter, read-only fetch with no output schema and annotations covering safety, the description is complete enough to call correctly, and it usefully indicates the kind of content returned. Only the missing routing guidance against siblings keeps it short of full marks.

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 described in the schema, including that a partial path from the slash onward is accepted. The description only echoes that a page address is supplied, adding no format or constraint detail beyond the schema, 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 states a specific verb and resource ("Abruf der Inhalte einer angegebenen Website-Seite") and narrows the payload to game details or a game list. What it does is clear, but there is no differentiation from siblings such as kostenlose_spiele or finder, so an agent cannot tell from the text alone which one to pick.

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, and no alternative is named. At best the phrase "Angaben zu einem Spiel oder die Liste der Spiele" implies the tool is for retrieving game data, leaving the agent to infer everything about routing.

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