Skip to main content
Glama

jackpots_de_casino

Read-only

L'outil renvoie le contenu d'une page à partir de son adresse, soit les faits concernant le jeu, soit la liste 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": "jackpots_de_casino"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCe paramètre reconnaît l'adresse complète de la page ou la portion qui commence par une barre oblique.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 safety is covered. The description adds a useful hint about the two possible response categories (game facts vs. game list), which goes beyond the annotations, but says nothing about failure behavior for bad URLs or how the returned content is structured.

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 front-loaded sentence with no padding. The 'soit ... soit ...' construction creates slight ambiguity about which output applies, but there is no wasted wording.

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?

With one required parameter, no output schema, and annotations covering safety, the definition is minimally adequate. However, it never ties the page retrieval to jackpot content despite the tool name, leaving an agent to guess how this differs from the sibling slot-machine tools.

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 coverage is 100% and the single 'url' parameter is fully documented, including the accepted full-address or leading-slash form. The description's 'à partir de son adresse' merely restates that, adding no new meaning; 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 a verb and resource ('renvoie le contenu d'une page à partir de son adresse'), but 'content of a page' is generic and never mentions jackpots, slots, or any casino-specific scope matching the tool name. The 'soit les faits concernant le jeu, soit la liste des jeux' clause hints at two possible response shapes without clarifying which page types produce which. An agent cannot confidently distinguish this from siblings like rechercher_machines_a_sous.

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 guidance on when to use this tool versus the sibling search/lookup tools, and no stated prerequisites for constructing a valid address. The only implied usage is 'give it a URL', which an agent could infer from the schema alone.

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