Skip to main content
Glama

Reelagio Slot Database

Find similar slots

similar_slots
Read-only

Find slots that play like a given slot, scored on mechanic, grid, volatility, max win, themes and features. Each match comes with a similarity score from 0 to 100 and the reasons it is similar. Use it for "games like X"; to filter by specs instead, use search_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": {
      "slot": "<slot>"
    },
    "name": "similar_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesSlot id, slug or name; a partial name or a small typo still resolves
limitNoHow many similar slots to return (1-25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 real value beyond them: it discloses the scoring dimensions, the 0-100 score range, and that each match carries human-readable reasons, which shapes how an agent should interpret output.

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?

Three sentences, front-loaded with the action and scoring basis, then the use case, then the alternative. No filler and nothing repeated from structured fields.

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?

No output schema exists, yet the description tells the agent what comes back: matches with a 0-100 similarity score and stated reasons. For a two-parameter read-only lookup, this is enough to select and invoke it correctly.

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%, so the schema already documents both params including the 1-25 limit bounds and the fuzzy name resolution. The description refers to 'a given slot' but adds no syntax or semantics beyond what the schema states; baseline 3 applies.

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 ('Find slots that play like a given slot') and enumerates the dimensions the match is scored on (mechanic, grid, volatility, max win, themes, features). The final clause names the sibling search_slots it is not, so an agent can distinguish the two without opening schemas.

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

Usage Guidelines4/5

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

Gives an explicit use case ('games like X') and an explicit routing rule to search_slots when spec filtering is wanted instead. Clear context and one named exclusion, though it doesn't cover edge cases like ambiguous names or what to do if no strong matches exist.

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