Skip to main content
Glama

Expertmachineasous FR

recherche_bandits_manchots

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. Total des avis: 27

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_bandits_manchots"
  }
}

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 and locality are covered. The description adds the useful constraint that matching is on page names only, but discloses nothing about matching semantics (case sensitivity, ranking, result limits) and ends with an unexplained 'Total des avis: 27' that reads as unrelated noise rather than behavioral detail.

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 scope plus exclusion. The trailing 'Total des avis: 27' does not earn its place, since it neither describes the tool's behavior nor helps an agent decide to call it.

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 search tool this is minimally adequate, and the name-only scope is made explicit. With no output schema, however, the description should say what a result actually contains (page name, type, identifier), and the dangling review count is left unexplained.

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 already documents the single parameter's meaning, the two-character minimum and the 64-character cap. The description's 'nom complet ou extrait' merely restates the schema, adding no new syntax or format guidance.

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: a search over page names that contain the entered text, scoped to games, game studios and collections. The exclusion of topic/theme/description searches sharpens the scope, though it never names a sibling tool for those cases.

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?

Gives a clear when-to-use condition (name-substring lookups) and an explicit when-not (searches by subject, theme or description are out of scope). It stops short of pointing to an alternative tool for the excluded cases, so the agent must infer where to go instead.

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