Skip to main content
Glama

top_jeux

Read-only

Fournit, pour une adresse de page donnée, le contenu présenté : les informations relatives au jeu ou 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": "top_jeux"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAdresse complète de la page ou partie commençant par une barre oblique.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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 nothing about behavior: whether the URL must belong to the site, what happens on an invalid address, how many games are returned, or whether results are paginated. For a lookup tool whose scope is a URL, this silence is a meaningful gap.

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?

It is a single sentence with no filler, and the input is front-loaded. However, the second clause ('les informations relatives au jeu ou la liste des jeux') is ambiguous rather than informative and reads as hedging, so brevity comes at the cost of clarity.

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?

There is no output schema and the description does not explain the return value. The description also leaves unexplained why the same tool yields two different shapes of content (game details vs. a list of games). For a read-only lookup that is the core question, this is incomplete.

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% (the url parameter is documented with relative-path support and a 300-character limit), so the schema carries the parameter burden. The description only repeats that a page address is required and adds no format or example detail, which matches the baseline of 3.

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 ('Fournit') and a resource ('le contenu présenté' for a given page URL), which is more than a restatement of the name. But the object is vague: it says the result is either game information or a list of games, so an agent cannot tell what this tool actually returns. It gives no hint of how it differs from siblings like top_jackpots.

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 or when-not-to-use guidance and no alternative is named. The related tools recherche_jeux and top_jackpots are never mentioned, so an agent has no basis for choosing among them beyond the tool name.

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