Skip to main content
Glama

rechercher_machines_a_sous

Read-only

Cette fonction localise les pages dont le nom comporte le texte donné : jeux, studios de jeux et collections. Les recherches par sujet, thème ou description ne sont pas couvertes. Total des 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": {
      "q": "<q>"
    },
    "name": "rechercher_machines_a_sous"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesNom 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.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 and world scope are covered. The description adds the useful behavioral detail that matching is on page name (not content), but says nothing about result ordering, limits or pagination for a lookup that could return many pages. The trailing 'Total des avis: 10' conveys no discernible 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 scope statement is front-loaded and efficient, and the exclusion sentence earns its place. However, 'Total des avis: 10' is unexplained noise that reads as a template artifact and dilutes an otherwise tight two-sentence 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 single-parameter, read-only lookup with annotations covering the safety profile and no output schema, the description supplies what matters: what is searched, how it matches, and what it does not cover. Only the shape of the returned result set (ordering, size) is left unaddressed, which is a minor gap here.

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 there is a single parameter, so the schema already documents 'q' with its min/max length and meaning. The description's 'texte donné' adds only a loose restatement, not format, casing or accent-handling details. 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 gives a specific verb ('localise') and resource ('les pages'), and pins down the match mode: pages whose NAME contains the given text, across games, game studios and collections. That is precise enough to act on, though it never names an alternative tool, so it stops short of full sibling differentiation.

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 explicitly states a negative scope: searches by subject, theme or description are not covered, which tells the agent when this tool will fail to answer. It does not name the tool that would handle those cases, so the routing guidance is incomplete but clearly present.

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