iGaming Tools — independent slot, provider & regulator reference data

Search & list slots

search_slots

Read-only

Search & list public slots (Pragmatic Play catalog). Also includes table games (blackjack, roulette, …) — game_category='table' items expose game_subtype (raw string, e.g. 'blackjack') alongside game_category; most slot-only fields (volatility, mechanic, reels/rows) are null for these. blackjack_payout and side_bets are detail-only — call get_slot for a table item to see them.

Text search:
  search: case-insensitive substring over slot name + aliases.
Release date:
  released_after / released_before: ISO date (YYYY-MM-DD), inclusive range on release_date.
  ordering: '-release_date' (newest first) or 'release_date' (oldest first);
    '-captured_at' (most recently captured from a live demo first) or 'captured_at'
    (oldest/never-captured first) — matches the public listing's default sort order.
    Paginate forward via the returned cursor for a complete set.
Structural filters:
  volatility: low/med_low/medium/med_high/high/very_high.
  mechanic: lines/ways/cluster/megaways/scatter_pays.
  jackpot_type: none/fixed/progressive/pooled/unknown.
  has_bonus_buy: 'true' | 'false'.
  provider / theme / feature / series: taxonomy slug filters, exact match on
    slug (not free text, not alias). An unknown slug returns an empty list,
    not an error — call list_themes / list_features / list_series to discover
    valid slugs, do not guess them from a search phrase. A slot belongs to at
    most one series.
  rtp_min / rtp_max: inclusive range filter on rtp_default (percent, decimal).
  game_category: unknown/video_slot/crash/instant_win/scratch/live/table/other —
    also selects/excludes table games (see docstring intro above).
  max_win_min / max_win_max: inclusive range filter on max_win (multiplier of
    stake, positive integer).
  These filters implicitly narrow the mix to slots (table items have these
  fields null and are excluded when a filter value is given), except
  game_category itself, which is how you select table games.
Pagination:
  cursor: opaque cursor from a previous response. page_size: items per page.
Each item exposes rtp_default (default-variant RTP as string or null), not 'rtp'.
Full RTP breakdown (rtp_variants), spec_sheet, symbols, palette and assets are ONLY in get_slot.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`theme`	No
`cursor`	No
`search`	No
`series`	No
`feature`	No
`rtp_max`	No
`rtp_min`	No
`mechanic`	No
`ordering`	No
`provider`	No
`page_size`	No
`volatility`	No
`max_win_max`	No
`max_win_min`	No
`jackpot_type`	No
`game_category`	No
`has_bonus_buy`	No
`released_after`	No
`released_before`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 5, 2026

addedInput schema / properties / series

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed5 schema fields changedJul 29, 2026

addedInput schema / properties / game_category

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / max_win_max

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / max_win_min

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / rtp_max

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / rtp_min

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedJul 18, 2026

TDQS

A5/5.0

Behavior5/5

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

The description discloses far beyond the readOnlyHint annotation: search is case-insensitive substring over name+aliases; unknown slugs return empty list, not error; filters implicitly narrow to slots except game_category; ordering semantics are explained; and the returned field is rtp_default not rtp. This is extensive behavioral context.

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

Conciseness5/5

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

Though long, it is organized with clear headers (Text search, Release date, Structural filters, Pagination) and every sentence adds essential guidance for a complex 19-parameter search tool. It is front-loaded with purpose and the critical table-game caveat. No redundant filler.

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

Completeness5/5

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

With 19 parameters, one annotation, and no param descriptions in the schema, this description covers all decision-relevant aspects: scope, filter semantics, ordering, pagination, data availability boundaries, and caveats about null fields. The presence of an output schema means return-value details don't need to be restated. It is fully complete for invocation and correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description compensates fully for all 19 parameters. It explains date formats, enum values for volatility/mechanic/jackpot_type, range filters with units (percent, multiplier), the meaning of game_category, and pagination via cursor/page_size. Every parameter is semantically defined beyond the schema's bare types.

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

Purpose5/5

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

The description clearly states it 'Search & list public slots (Pragmatic Play catalog)' and expands to table games, including a boundary that 'most slot-only fields are null' for table items. This differentiates it from get_slot (which provides details) and other sibling tools by naming what this search covers and what it doesn't.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use vs alternatives: 'call get_slot for a table item to see blackjack_payout and side_bets', and 'call list_themes / list_features / list_series to discover valid slugs' for taxonomy filters. It also states that full RTP breakdown and other rich data are 'ONLY in get_slot', preventing misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All iGaming Tools — independent slot, provider & regulator reference data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?