Skip to main content
Glama

random

Generate secure integers, floats, UUIDs, passwords, dice rolls, coin flips, bytes, choices, and shuffles, with optional seeds for reproducible results.

Instructions

Secure random: int (any size, inclusive, unique), float, normal, choice, shuffle, uuid, password, dice ("4d6kh3+2"), coin, bytes. seed = reproducible.

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

Input Schema

NameRequiredDescriptionDefault
sdNo
maxNo
minNo
diceNo
kindNo
meanNo
seedNo
countNo
itemsNo
lengthNo
uniqueNo
charsetNolower,upper,digits,symbols
decimalsNo
no_ambiguousNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses two important traits—'Secure' implies cryptographic randomness and 'seed = reproducible' signals deterministic seeding—but it says nothing about output formats, error conditions, or per-mode security guarantees.

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 definition is a single compact sentence with no filler and the mode list is front-loaded. However, the dense run-on list is hard to scan and does not structure the mapping from modes to parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter tool with no annotations, no output schema, and 7% schema coverage, the description is far too sparse. It enumerates modes but does not explain defaults, parameter interactions, or return values, so an agent would need to guess how to invoke most modes correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 7% across 14 parameters. The description adds meaning for a few—kind modes, unique, seed reproducibility, dice notation, and possibly inclusive min/max—but leaves sd, mean, count, items, length, charset, decimals, and no_ambiguous unexplained.

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?

The description identifies a secure random generator and enumerates the supported modes (int, float, normal, choice, shuffle, uuid, password, dice, coin, bytes), so an agent can tell what the tool produces. It is a fragment rather than a full verb+resource statement, but the mode list is specific enough to distinguish it from unrelated siblings like calc or hash.

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

Usage Guidelines2/5

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

Only 'seed = reproducible' offers a usage hint; there is no guidance on when to choose each kind, which parameters apply to which mode, or what the default behavior is. No alternatives are named, and the 14-parameter surface is left for the caller to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.