Skip to main content
Glama

bandits_manchots_resultats

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: 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": {
      "recherche": "<recherche>"
    },
    "name": "bandits_manchots_resultats"
  }
}

Input Schema

NameRequiredDescriptionDefault
rechercheYesLa valeur correspond au nom ou à un élément du nom d’un jeu, d’un studio ou d’une collection, à condition 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 profile is covered. The description usefully adds that matching is on name only and that other search fields are excluded, but the trailing 'Total des avis: 18' is unexplained and appears unrelated to the tool's behavior, weakening transparency.

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 scoping sentence is front-loaded and efficient, and the exclusion sentence earns its place. The final fragment about a review total is noise that adds no actionable information and leaves the reader unsure whether it is a result-value hint or an artifact.

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 lookup with full schema coverage and existing annotations, the essentials are present. However, with no output schema, the description gives no indication of what a result looks like or how many results to expect, and the stray review-total text is 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%, so the single 'recherche' parameter is already documented in the schema, including the two-character minimum. The description repeats the same notion (an element of a game, studio or collection name) without adding syntax, format or matching-rule detail beyond the schema.

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 operation (search for pages whose name contains the input text) and scopes the resource precisely to games, game studios and collections. It is clear what the tool does, though it does not explicitly contrast itself with the sibling tools top_bandits_manchots or rouleaux_populaires.

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 states an explicit exclusion: searches by subject, theme or description are not supported. That gives a usable when-not boundary, but it never names an alternative tool to use for those other search modes, so guidance stops short of full 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