Skip to main content
Glama

Retro Spielautomat AT

suche

Read-only

Die Suche vergleicht den eingegebenen Text mit dem Namen von Seiten zu Spielen, Spielstudios und Kollektionen. Thema, Motiv und Beschreibung fließen nicht ein. Getestete Spiele: 9

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": {
      "s": "<s>"
    },
    "name": "suche"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesDer Suchbegriff besteht aus dem Namen oder einem Teil des Namens eines Spiels, eines Spielestudios oder einer Sammlung und umfasst mindestens zwei Zeichen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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-domain behavior are covered. The description adds genuine behavioral context beyond that: matching is name-only, so thematic queries silently return nothing. It omits result ordering, limits, and match semantics (substring vs prefix), and the closing 'Getestete Spiele: 9' line is unexplained and reads as leakage.

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 core scope statements are front-loaded and efficient. The final fragment 'Getestete Spiele: 9' does not earn its place: it is opaque, likely a test artifact, and distracts from the routing information.

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-only, closed-domain search with full schema coverage and no output schema, the description covers what is and is not matched, which is the main correctness risk. It still leaves result shape, ordering, and whether matching is substring or prefix unstated.

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 schema already says the term is a name or partial name of a game, studio, or collection with a two-character minimum. The description mainly restates that, adding only the negative constraint that topic, motif, and description are not searched, so it marginally exceeds baseline but does not compensate further.

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 operation (comparing the entered text against page names) and enumerates the target resources: games, game studios, and collections. It also sharply delimits scope by excluding topic, motif, and description. It does not name the sibling tools, so sibling differentiation is only implicit.

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?

The exclusion of topic/motif/description implicitly tells the agent this is a name-lookup and not a thematic search, which is useful routing context. However, no alternative tool or explicit 'use this when / not when' statement is given, and the ambiguous trailing note 'Getestete Spiele: 9' does not clarify usage.

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