Skip to main content
Glama

top_jackpots

Read-only

Cette fonction renvoie les collections de jeux du site et l'adresse de la page associée à 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_jackpots"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already state that this is a read-only operation on a closed system, so the safety profile needs no restatement. The description adds the shape of the result at a high level: a collection plus the URL of its associated page. It does not explain how many collections come back, whether the list is paginated, or the ordering.

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 core sentence is tight and comes first, which is good. The trailing "Toutes les collections: 1" is a dangling fragment that reads as truncated or machine-generated and does not add interpretable meaning. One sentence of the description is wasted.

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 zero-parameter, read-only tool with no output schema, the description must carry the burden of explaining the result. It states the two fields returned (collection and page URL) but not their structure, cardinality, or content. It is just enough to attempt a call, but an agent cannot predict the return payload well.

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, so correctness of invocation does not depend on parameter documentation. The schema is empty by design, and the description correctly implies that there is nothing to supply. No semantic gap exists for parameters.

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 names a concrete verb and resource ("renvoie les collections de jeux du site et l'adresse de la page associee a chacune"), so the basic operation is understandable. However, it does not line up with the tool name top_jackpots, and nothing distinguishes it from the siblings top_jeux and recherche_jeux. The trailing fragment "Toutes les collections: 1" adds ambiguity rather than precision.

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 guidance is given about when to call this tool instead of the siblings, and there are no stated prerequisites or exclusions. The agent has to guess that it returns a site-wide list rather than a filtered search. The only implicit cue is the phrase "Toutes les collections".

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