Skip to main content
Glama

Spin the wheel

spin_wheel
Read-only

Use this when the user wants to spin the wheel, use a wheel spinner or random name picker, pick a random name or option from a list (wheel spinner with names, yes or no wheel, food wheel, custom wheel), or call on people one at a time. Draws 1 or more different winners with cryptographic, unbiased randomness and shows an animated wheel that lands on the winner. Repeated entries (matched ignoring case) or weights give bigger slices. Returns the winners, each entry's chance, and the remaining entries when remove_winners is true. For fun, classroom, and team decisions only; not for lotteries, gambling, or prize draws that have legal requirements. Does not store results between calls.

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": {
      "entries": "<entries>"
    },
    "name": "spin_wheel"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many different winners to draw in this spin, a whole number from 1 to 50, default 1, e.g. 3 to pick 3 students.
titleNoOptional wheel title shown above the wheel, e.g. "Who presents first?".
entriesYesThe names or options on the wheel, 2 to 200, e.g. ["Ana", "Ben", "Chloe"]. A repeated entry gets a bigger slice: ["Pizza", "Pizza", "Tacos"] gives Pizza 2 of 3 slots.
weightsNoOptional whole-number weight (1-1000) per entry, same order and length as entries, e.g. [3, 1, 1] makes the first entry three times as likely. Leave out for equal chances.
remove_winnersNoIf true, the winners are taken off the wheel and the remaining entries are returned for the next spin, e.g. true for calling on each student once.

Output Schema

NameRequiredDescriptionDefault
kindYes
titleYes
entriesYes
removedYes
weightsYes
winnersYes
remainingYes
chance_percentYes
winner_indexesYes
remaining_weightsYes
equal_chance_percentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, non-destructive, non-idempotent behavior, but the description adds substantial context: cryptographic unbiased randomness, animated wheel behavior, how repeated entries/weights affect slices, what is returned (winners, chances, remaining entries when remove_winners is true), and that results are not stored between calls. These details are not in the annotations and are valuable for correct invocation.

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?

The description is front-loaded with usage guidance and covers all key points, but it runs to five sentences and includes some redundant explanation that could be trimmed. It is well-structured overall, though not maximally concise.

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?

Given the tool's moderate complexity, with full schema coverage, annotations, and an output schema, the description provides everything an agent needs: when to use, limitations, randomness guarantees, parameter effects, return behavior, and statelessness. No critical gaps remain.

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 description coverage is 100%, so the schema already documents all five parameters thoroughly. The description adds minor semantics like case-insensitive matching for repeated entries and clarifies the return values, but does not significantly extend the parameter meaning beyond what the schema provides.

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 states a specific verb (spin/draw) and resource (wheel/entries) and clearly distinguishes from pick_random_number by specifying selection from a list. The many examples (wheel spinner, name picker, yes/no wheel) make the tool's purpose unmistakable.

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?

It gives explicit when-to-use cases ('when the user wants to spin the wheel...') and a clear when-not exclusion ('not for lotteries, gambling, or prize draws that have legal requirements'). It does not name sibling tools as alternatives, so it falls short of the top score.

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