Skip to main content
Glama

top_bandits_manchots

Read-only

Le site publie des collections de jeux. Cette liste indique l'adresse de la page de chacune. 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": "top_bandits_manchots"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only that page URLs are listed, but the trailing "Toutes les collections: 1" contradicts the notion of a full listing and gives no clue about result shape, ordering, or what the "1" refers to.

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 description is short but poorly structured: the core statement about page addresses is buried in the second sentence, and the trailing "Toutes les collections: 1" adds confusion rather than information. It is brief, but not front-loaded or well-formed.

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?

For a simple zero-parameter listing tool with no output schema, the description is the only source of return-value context, and it fails to explain what the list actually contains or why it says "1". An agent cannot confidently predict the output before calling it.

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 takes zero parameters and the schema is fully described, so there is nothing for the description to disambiguate. Baseline 4 applies; no additional parameter meaning is needed.

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

Purpose2/5

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

The description says the site publishes game collections and that "this list gives the address of each one's page," which hints at a URL listing, but the resource and verb are never named clearly and the tool name plus the fragment "Toutes les collections: 1" (all collections: 1) actively muddies what is returned. Nothing distinguishes it from siblings like bandits_manchots_resultats 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 Guidelines2/5

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

There is no when-to-use guidance, no conditions, and no mention of when a different tool would be preferable. The agent must infer the purpose entirely from an ambiguous title and a three-sentence fragment.

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