Skip to main content
Glama

jackpots_suche

Read-only

Sucht Seiten dieser Website, deren Name den angegebenen Text enthält; erfasst werden Spiele, Spielstudios und Kollektionen. Keine Suche nach Thema, Motiv oder Beschreibung. Getestete Spiele: 20

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

Input Schema

NameRequiredDescriptionDefault
sYesGesucht wird nach dem Namen oder einem Namensteil eines Spiels, eines Spielestudios oder einer Sammlung, mit einer Mindestlänge von 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 the safety profile is covered. The description adds useful scope detail (name-only matching across three entity classes), but the trailing 'Getestete Spiele: 20' is cryptic and unexplained – it hints at a coverage limitation without stating what the agent should conclude from it.

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?

The core scope and the exclusion are front-loaded in two tight clauses with no filler. The final fragment 'Getestete Spiele: 20' is unearned because it is never explained or connected to agent behavior.

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 search with no output schema, the description supplies enough to call it correctly: what is matched, what entity types are returned, and what is out of scope. The only incompleteness is the unexplained 'Getestete Spiele: 20' note, which leaves a coverage caveat 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 coverage is 100% and the single parameter already documents min length, max length, and that partial names are accepted. The description's 'enthält den angegebenen Text' reinforces substring matching but adds nothing the schema does not already say, 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 names a specific verb and resource ('Sucht Seiten dieser Website, deren Name den angegebenen Text enthält') and enumerates the covered entity types (Spiele, Spielstudios, Kollektionen). It is clear what the tool does, but it does not name or contrast itself with the sibling tools jackpots and automaten, leaving that differentiation to inference.

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?

It gives an explicit exclusion: 'Keine Suche nach Thema, Motiv oder Beschreibung', which tells the agent when this tool will fail to match. It stops short of pointing to an alternative tool for thematic search, so there is no explicit when-to-use-instead 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