Skip to main content
Glama

recherche_jeux

Read-only

Recherche de pages dont le nom contient le texte saisi : jeux, studios de jeux et collections. Les recherches par sujet, thème ou description sont exclues. Tests et avis: 10

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

Input Schema

NameRequiredDescriptionDefault
sYesNom complet ou extrait du nom d’un jeu, d’un studio ou d’une collection, longueur minimale de 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 safety is covered; the description usefully adds that matching is a name-substring match and not a topical search. It says nothing about result ordering, caps, or pagination, and the trailing fragment 'Tests et avis: 10' is opaque rather than informative.

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 first two sentences are tight and front-loaded with the matching rule before the exclusion. The final fragment 'Tests et avis: 10' is unexplained and reads as a stray artifact, weakening an otherwise efficient 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 single-parameter read tool with annotations present and no output schema, the core matching semantics are adequately conveyed. The undefined trailing note and the absence of any indication of result volume or ordering leave a noticeable 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 schema already documents the single 's' parameter with its 2–64 character bounds and its role as full or partial name. The description only restates that it is a name-substring match, adding little beyond the structured field, so 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?

States a specific verb and resource ('Recherche de pages') and narrows the scope to name matches over games, studios and collections, which is enough to distinguish it from the ranking-oriented siblings top_jeux and top_jackpots. It stops short of naming an alternative, but the operation itself is unambiguous.

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?

Explicitly rules out subject, theme and description searches ('Les recherches par sujet, thème ou description sont exclues'), which is real when-not guidance. It never names an alternative tool to use for those excluded cases, so routing is only partly solved.

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