iGaming Tools — independent slot, provider & regulator reference data

Get slot series

get_series

Read-only

Get a slot series (game family) summary: aggregate stats plus a short roster.

slug: series slug (from list_series results).
Returns slots_count, years/rtp/max_win ranges, and distributions
(volatility, has_bonus_buy, game_category — each sums to slots_count,
including 'unknown'/null buckets) computed over the family's public
slots. slots is a short roster, newest release first; if slots_truncated
is true the roster was capped — use slots_url (or
search_slots(series=<slug>)) to fetch the complete list.
404 if the slug is unknown or the series has no public slots.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 5, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behaviors: aggregate stats computed over public slots, inclusion of unknown/null buckets in distributions, roster sorted newest first, truncation flag, and 404 conditions for unknown slugs or no public slots. This adds significant transparency.

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?

The description is dense but well-structured: a concise summary followed by parameter detail, return value explanations, truncation behavior, and error cases. Every sentence adds value without redundancy.

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?

Even though an output schema exists, the description provides a thorough overview of return values (slots_count, ranges, distributions, roster), truncation semantics, and error responses. This makes the tool's behavior fully understandable and complete for an agent.

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?

The schema has zero description coverage, so the description fully carries the burden. It explains the 'slug' parameter as coming from list_series results, which is essential context not inferable from the schema alone. This is sufficient for correct invocation.

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 the tool retrieves a slot series summary with aggregate stats and a short roster, using a specific verb ('Get') and resource ('slot series'). It distinguishes itself from sibling tools like list_series (which lists series) and get_slot (single slot detail).

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?

Explicit guidance is provided: the slug comes from list_series results, and alternatives (slots_url or search_slots with series filter) are named for obtaining the complete roster when truncated. This clearly indicates when to use this tool versus other options.

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?