Skip to main content
Glama

Slots Diamant FR

rouleaux_recherche

Read-only

La recherche porte sur les noms de pages : jeux, studios de jeux et collections. Elle ne s'applique ni aux sujets, ni aux thèmes, ni aux descriptions. Avis sur les jeux: 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": {
      "q": "<q>"
    },
    "name": "rouleaux_recherche"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesNom ou partie du nom d’un jeu, d’un studio ou d’une collection, d’au moins deux caractères.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 and locality profile is covered. The description adds the useful detail that only name fields are indexed, but says nothing about result size, ordering, pagination or fuzzy matching. The closing 'Avis sur les jeux: 18' fragment is unexplained and adds ambiguity rather than behavioral clarity.

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 scoping sentences are tight and front-loaded with the positive scope before the exclusions. However, the dangling 'Avis sur les jeux: 18' fragment is unexplained noise that weakens an otherwise lean definition.

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 one-parameter, read-only, closed-world search tool with a fully described schema, the description covers the essential scope question. It falls short on what comes back — no mention of result count, ordering or whether partial-word matches are supported — and with no output schema the description is the only place that could say so.

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 q parameter is fully documented in the schema (name or partial name, minimum two characters). The description corroborates the semantics by listing the three name categories searched, but adds no syntax, casing or matching rules beyond the schema. 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 the verb (recherche) and pins down the exact field scope: page names of games, game studios and collections. That is specific enough to distinguish it from a general content search. It does not differentiate itself from the sibling tools rouleaux_en_ligne or jackpots_sans_telechargement, which is why it stops short of a 5.

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 clearly states the negative case — the search does not apply to subjects, themes or descriptions — which tells an agent when a query will return nothing. It offers no alternative tool to use instead, and the trailing 'Avis sur les jeux: 18' gives no usable guidance at all.

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