Skip to main content
Glama

rouleaux_populaires

Read-only

Renvoie, d'après l'adresse d'une page, les éléments visibles de cette page : le détail du jeu ou l'inventaire des jeux.

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": {
      "url": "<url>"
    },
    "name": "rouleaux_populaires"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLe champ accepte l'adresse complète de la page ou la partie commençant par une barre oblique.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 does add behavior beyond that by disclosing that it extracts visible page content and can return one of two distinct payloads (game detail or game inventory). It falls short of explaining what condition selects one mode over the other, or what either payload contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the input ('d'après l'adresse d'une page') stated before the output, so it is front-loaded and free of padding. It is efficient, though the phrase 'éléments visibles' costs some precision for its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries full responsibility for explaining return values, and it only names two possible payloads without saying when each occurs or what they contain. For a two-mode scraping tool this leaves the agent unable to predict the response. Annotations cover safety but not output shape.

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 URL format (full address or leading-slash path) is already documented in the schema. The description's 'd'après l'adresse d'une page' only restates that the parameter is a page address, adding no syntax, constraints, or examples beyond structured data. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb ('Renvoie') and the resource ('les éléments visibles de cette page'), and narrows the output to 'le détail du jeu ou l'inventaire des jeux'. However, 'éléments visibles' is vague about what extraction actually happens, and nothing connects the cryptic name 'rouleaux_populaires' to the domain the siblings imply. An agent can guess it is a page-scraper but not confidently what its output represents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance is given: nothing says whether this should be called instead of the sibling tools (bandits_manchots_resultats, top_bandits_manchots) or alongside them. There are no prerequisites, no exclusions, and no indication of which pages are valid targets.

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