Skip to main content
Glama

Reelagio Slot Database

Search slots

search_slots
Read-only

Search the Reelagio database of online slot games. Use it to find slots by name, or by any mix of provider, theme, feature, volatility, mechanic, max win and bonus buy. Filters combine with AND. Values are matched loosely ("pragmatic" finds Pragmatic Play, "fishing" finds the underwater theme), and query also understands a plain description such as "high volatility fishing slots with bonus buy". Returns up to limit slots, most popular first unless sort says otherwise, each with its specs and a link to its page, plus total matches. When nothing matches, the result says which value was not recognised or which filters clash, and lists the valid values. For the full spec sheet of one slot use get_slot.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of results: most popular first, or highest max win firstpopularity
emojiNoEmoji tags the slot must have, e.g. "🐵🏛️" (ALL must match)
limitNoHow many slots to return (1-25)
queryNoA slot name or part of one ("big bass"), or a plain description of what to find ("megaways slots over 20,000x")
themesNoSlot must have ANY of these themes, e.g. ["western"], ["egyptian", "greek"]
bonusBuyNoOnly slots with (true) or without (false) a bonus buy
featuresNoSlot must have ALL of these features, e.g. ["free spins", "sticky wilds"]
gameTypeNoHow wins are formed: fixed (paylines), ways, megaways, cluster (cluster pays), scatter (pay anywhere) or collect
providerNoGame studio, e.g. "Pragmatic Play"; part of the name is enough
minMaxWinNoMinimum max win as a multiple of the bet, e.g. 10000 for 10,000x
volatilityNoSlot volatility is ANY of these

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds substantial behavior beyond that: filters combine with AND, values match loosely, query accepts natural language, results are capped at limit and sorted by popularity by default, each result carries specs plus a page link and a total count, and failures explain which value was unrecognised and list valid values. Only minor gaps remain (e.g. pagination beyond limit).

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?

Front-loads the core purpose, then layers matching semantics, return shape, and the sibling pointer in a tight sequence. Dense but every sentence carries information an agent needs; no 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?

For an 11-parameter, zero-required search tool with no output schema, the description covers matching behavior, result ordering, return contents (specs, link, total), and error behavior. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: loose matching semantics ("pragmatic" finds Pragmatic Play), that query accepts a plain description, and the AND combination rule across filters. This goes beyond the schema's per-parameter text.

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?

States a specific verb and resource ("Search the Reelagio database of online slot games") and immediately distinguishes itself from the sibling get_slot ("For the full spec sheet of one slot use get_slot"). An agent can tell exactly what this tool returns versus the alternatives.

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 says when to use it (find slots by name or any mix of filters, or a plain-language description) and names the alternative for the other case (get_slot for a single slot's full spec sheet). The routing decision is fully specified.

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