Skip to main content
Glama

Pick random numbers

pick_random_number
Read-only

Use this when the user wants a random number generator or number wheel: pick one or more random whole numbers between a min and a max (inclusive), with or without repeats, e.g. a random student number or who goes next. Uses cryptographic, unbiased randomness. Do not use for lottery or Powerball numbers, betting, or login credentials and security codes. For fun, classroom, and team decisions only; not for lotteries, gambling, or prize draws that have legal requirements.

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

Input Schema

NameRequiredDescriptionDefault
maxNoLargest possible whole number, inclusive, -1000000000 to 1000000000, default 100, e.g. 30 for a class of 30.
minNoSmallest possible whole number, inclusive, -1000000000 to 1000000000, default 1, e.g. 1.
countNoHow many numbers to pick, a whole number from 1 to 500, default 1, e.g. 5.
uniqueNoIf true (default) no number repeats, e.g. false to allow repeats like dice rolls.

Output Schema

NameRequiredDescriptionDefault
maxYes
minYes
kindYes
countYes
uniqueYes
numbersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false, so safety is covered. The description still adds meaningful context not in the annotations: cryptographic unbiased randomness, inclusivity of bounds, and the repeat-vs-no-repeat semantics, plus a non-security/non-gambling scope limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The use case is front-loaded well, but the closing two sentences duplicate the same prohibition twice — 'Do not use for lottery or Powerball numbers, betting...' is immediately followed by 'not for lotteries, gambling, or prize draws that have legal requirements.' One of these could be cut without losing information.

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?

With an output schema present, return values need no explanation, and the four simple parameters are fully covered by schema. The description supplies the safety/scope boundary and randomness quality, leaving little an agent would need to call it correctly. Only the sibling boundary (spin_wheel) remains underspecified.

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 all four parameters (min, max, count, unique) are already documented with ranges, defaults, and examples. The description's 'inclusive' and 'with or without repeats' restate what the schema already says, adding no new syntax or constraints beyond the baseline.

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?

States a concrete verb and resource ('pick one or more random whole numbers between a min and max, inclusive') with the repeat behavior spelled out. Differentiation from siblings is only implicit — the phrase 'number wheel' arguably overlaps with spin_wheel, and make_teams is never contrasted, so the agent must infer the boundary.

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 names when to use it (random student number, who goes next, classroom and team decisions) and lay out concrete exclusions (lottery, Powerball, betting, login/security codes, legal prize draws). This is exactly the when/when-not routing an agent needs.

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