Skip to main content
Glama

top_jackpots

Read-only

The themed collections of games published on this website and the page address of every collection. Themed collections of games: 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

C2.1/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that collection page addresses are included, but says nothing about the number of results, ordering, structure, or what a collection record contains. The stray ': 1' suggests truncated or machine-translated content rather than deliberate behavior disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short but not front-loaded or coherent: two overlapping restatements of 'themed collections of games' plus a dangling numeric fragment. The duplicated content and the unexplained ': 1' are noise that a cleaner sentence would remove.

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?

With no output schema, the description must explain what comes back, and it does so only vaguely ('the page address of every collection'). For a zero-parameter read tool the bar is low, yet the garbled text and name/description mismatch leave the agent unsure of the return shape and of how this differs from search.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter claims are made.

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 text is a noun phrase listing content ('the themed collections of games ... and the page address of every collection') rather than a verb-plus-resource statement of what the tool does. It also diverges from the tool name top_jackpots with no explanation of the relationship, and the trailing fragment 'Themed collections of games: 1' carries no discernible meaning, leaving the agent to guess that this is a list/retrieval tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 mention of when not to use it, and no reference to the sibling tools free_pokies or search. An agent cannot infer from the description alone whether this overlaps with search.

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