Skip to main content
Glama

suchen_slots

Read-only

Namenssuche über Seiten zu Spielen, Spielstudios und Kollektionen; der eingegebene Text muss im Namen vorkommen. Thema, Motiv und Beschreibung werden nicht herangezogen. Anzahl der Spieltests: 4

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": {
      "q": "<q>"
    },
    "name": "suchen_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesName oder Teil eines Namens von Spiel, Spielestudio oder Sammlung, mindestens zwei Zeichen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 is covered. The description adds that matching is strictly name-based, which is useful behavioral context, but the trailing note 'Anzahl der Spieltests: 4' is cryptic and never explained, and there is no mention of result limits, pagination or what the results contain.

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?

Three short sentences, front-loaded with the search scope before the exclusion rule. Nothing is padded, but the unexplained 'Anzahl der Spieltests: 4' clause adds noise without meaning for the calling agent.

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 search with full schema coverage and annotations, the description covers scope, matching rule and exclusions adequately. Return shape and pagination are not covered, but no output schema exists to compensate for that, so it remains a minor gap.

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 parameter already documents itself as a name or partial name of at least two characters. The description's statement that the text must appear in the name largely restates the schema, though it does reinforce substring (not fuzzy) matching semantics.

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 operation (name search) and enumerates the three resource types searched: games, game studios and collections. It also states the matching rule (the query must occur in the name). It does not name the sibling 'spiele' or explain how this differs from it, so sibling differentiation is left implicit.

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

Usage Guidelines4/5

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

The description gives a clear negative guideline: topic, motif and description are NOT used for matching, which tells the agent to look elsewhere for thematic search. It stops short of naming which alternative tool to use for those cases, but the when-to-use condition (exact/partial name lookup) is unambiguous.

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