Skip to main content
Glama

rouleaux_en_ligne

Read-only

Liste des collections de jeux publiées sur le site, avec l'adresse de leur page. Toutes les collections: 1

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rouleaux_en_ligne"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world operation. The description adds only that the result includes page addresses, while saying nothing about pagination, result count, ordering, or what the opaque '1' refers to, so behavioral value beyond the annotations is minimal.

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 main sentence is appropriately short and front-loaded, but the trailing fragment 'Toutes les collections: 1' does not clearly earn its place and introduces ambiguity rather than useful structure.

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 simple, parameterless read-only lister with no output schema, the description covers the essentials: what is listed and that page addresses are included. However, the unexplained '1' and the absence of any return-shape or usage context leave it only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing for the description to disambiguate. The baseline for a parameterless tool is 4, and no parameter-related gaps are present.

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 uses a specific verb, 'Liste', and a clear resource, 'collections de jeux publiées sur le site', plus the useful detail that each entry includes its page address. It does not differentiate from the sibling tools, and the trailing 'Toutes les collections: 1' is cryptic enough to slightly weaken clarity.

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?

There is no explicit guidance on when to use this tool versus the sibling tools, nor any stated preconditions or exclusions. The description only implies that it is a listing operation, leaving selection entirely to inference.

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