Skip to main content
Glama

Reelagio Slot Database

Get slot details

get_slot
Read-only

Get the full spec sheet for one slot: provider, grid, paylines or ways, mechanic, volatility, max win, features, themes, bonus buy, minimum bet, release date, whether a free demo is available, the other games in its series and, where Reelagio has one, a short write-up of how it plays. Accepts a slot id, URL slug or name; a partial name or a small typo still resolves, and the result then says which slot was picked and what else it could have meant.

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

Input Schema

NameRequiredDescriptionDefault
slotYesSlot id, slug or name, e.g. "gates-of-olympus" or "Gates of Olympus"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral detail: fuzzy resolution of partial names and typos, and the fact that the response reports which slot was chosen plus what else it could have meant. Conditional data presence is also disclosed ("where Reelagio has one, a short write-up"). It does not say what happens when nothing matches.

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?

Front-loaded with the core purpose in the first clause, then a deliberately long field enumeration that earns its place by telling the agent what it will get. The second sentence on identifier flexibility and disambiguation is compact and non-redundant; the field list is dense but not padded.

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?

No output schema exists, so the description carries the return-value burden, and it does so by enumerating the spec fields and the disambiguation report. With only one required parameter and a fully described schema, the remaining gap is failure behavior on a non-resolving name, which is minor.

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% and the schema already documents the single slot parameter, so the baseline is 3. The description adds meaning beyond that by stating the identifier is accepted as id, URL slug or name, and that partial names and small typos still resolve — tolerance semantics the schema does not convey.

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?

Specific verb and resource ("Get the full spec sheet for one slot") followed by an explicit enumeration of the returned fields, so an agent can tell this is the single-slot detail lookup rather than a search. It never names a sibling, so differentiation from search_slots/similar_slots is inferred from the field list rather than stated.

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?

Usage is implied by the phrase "for one slot" and by the accepted identifier forms, which suggests it is for known-slot lookups. There is no explicit when-not-to-use guidance and no routing to search_slots when the user has no name at all, though the partial-name/typo tolerance partially covers that case.

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