Skip to main content
Glama

GambleMath — Casino RTP, Bonus EV & UKGC Register Lab

audit_slot_rtp

Retrieve technical specs, published RTP profile(s), max win multiplier, and bankroll half-life for any of 4,362 catalog slots.

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": {
      "slug": "<slug>"
    },
    "name": "audit_slot_rtp"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlot slug (e.g. sweet-bonanza, gates-of-olympus, wanted-dead-or-a-wild, book-of-dead)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the shape of the payload (specs, RTP profiles, max win, bankroll half-life), which implies a read-only lookup, but it says nothing about error behavior for an unknown slug, whether RTP profiles span multiple jurisdictions, or response size.

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?

One efficient, front-loaded sentence with no filler; the verb comes first and the return payload is enumerated immediately. The field list is dense but each item is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup with no output schema, enumerating the returned fields in the description usefully compensates for the missing return definition. Only edge-case behavior (unknown slug, multi-jurisdiction RTP) is unaddressed.

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 slug parameter is already documented with four concrete examples, so the schema does the heavy lifting. The description adds only that the slug must be one of 4,362 known catalog entries, which is marginal extra meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Retrieve') with a named resource and enumerates the returned data: technical specs, RTP profile(s), max win multiplier, bankroll half-life. An agent can tell this is a slot-data lookup and that it is distinct from parlay, domain, and bonus-EV siblings, though it never names an alternative explicitly.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage only: 'for any of 4,362 catalog slots' communicates coverage scope but gives no when-to-use, when-not-to-use, or prerequisite guidance. There is no statement about what to do when a slug is not in the catalog.

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