Skip to main content
Glama

best_jackpots

Read-only

Given the address of a page, returns what the page shows: the details of one game or its list of games.

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": "best_jackpots"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull page address or a slash-prefixed fragment of this site.

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 and scope are covered. The description adds the useful behavioral detail that the response shape varies — either a single game's details or a list of games — which is genuine context beyond the annotations, though it does not explain error behavior or how the two response shapes are distinguished.

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 well-formed sentence with no filler, and the input condition ("Given the address of a page") is front-loaded ahead of the return value. It is efficient, though slightly under-specified rather than over-long.

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?

The tool is simple (one required parameter, no output schema, no nesting), and the description covers the input and hints at the variable return shape. It still leaves open what a "game" record contains and why the tool is named best_jackpots, which matters since no output schema exists to fill that gap.

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% for the single url parameter, and the schema already specifies "full page address or a slash-prefixed fragment of this site". The description's "address of a page" restates this without adding format or constraint detail, so 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 names a verb ("returns") and a resource (page content: "the details of one game or its list of games"), so an agent can infer it is a page-fetch tool. However, it never mentions "jackpots", the tool's namesake, and gives no basis for choosing it over siblings best_machines or find_games, so its purpose stays vague relative to the catalog.

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 prerequisites, and no reference to alternatives such as find_games for discovery or best_machines for machine data. The agent must guess which of the siblings returns jackpot listings.

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