Skip to main content
Glama

Crashgames Casino AT

finder

Read-only

Die Abfrage beschränkt sich auf Seitennamen von Spielen, Spielstudios und Kollektionen. Thema, Motiv und Beschreibung werden nicht ausgewertet. Rezensionen zu Spielen: 18

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

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.4/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 usefully adds that matching is name-only across three page types, which is real behavioral context an agent cannot get from annotations, but it says nothing about result volume, ranking or pagination. The stray 'Rezensionen zu Spielen: 18' line is opaque and adds no interpretable behavior.

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 two lead sentences are terse and front-load the matching scope, which is good. The final fragment 'Rezensionen zu Spielen: 18' is unexplained and reads as leftover noise, weakening an otherwise lean description.

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 one-parameter, read-only lookup with full schema coverage and no output schema, the definition covers the important question of what is matched and what is ignored. Only the return shape (single page vs. list of pages) and the meaning of the trailing fragment are left ambiguous.

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 description coverage is 100% and the single 's' parameter is already documented as a full or partial name with a two-character minimum. The description repeats the scope of that string but adds no new meaning such as case sensitivity, whitespace handling or partial-match rules, so the baseline of 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 scopes the tool to matching page names of games, studios and collections, and explicitly excludes topic, motif and description from evaluation, which tells an agent what kind of lookup this is. The verb itself is only implied ('Die Abfrage'), and no sibling tool is named for contrast, so the tool's identity is clear but not sharply differentiated from the generic 'spiele' sibling.

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 sentence about topic, motif and description not being evaluated gives an implicit when-not-to-use signal: do not call this for thematic or content search. However, no explicit conditions, no named alternatives, and the trailing review-count fragment provides no actionable guidance.

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