Dice Roller

Dice Odds

dice_odds

Read-onlyIdempotent

Pipeworx dice engine: the probability distribution of a dice notation (same grammar as roll_dice: 2d6+3, 4d6kh3, 2d20kl1, 4dF, 3d6!) — min, max, mean, standard deviation, mode, the probability of every total and, given target, the chance the total is >=, >, <=, < or == that target (e.g. "what are the odds of 15 or more on 3d6"). Exact by enumeration where the outcomes can be enumerated (plain sums, and keep/drop pools up to 1,000,000 outcomes); otherwise a 100,000-sample Monte Carlo estimate labelled method:"monte_carlo" (exploding dice always use it). seed makes a Monte Carlo estimate reproducible.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": 15,
      "notation": "3d6",
      "comparison": ">="
    },
    "name": "dice_odds"
  }
}

Input Schema

Name	Required	Description
`seed`	No	Optional seed for the Monte Carlo path; exact results ignore it. Always returned.
`target`	No	Optional target total to compute a probability for.
`notation`	Yes	Dice notation, e.g. "3d6", "4d6kh3", "2d20kh1+5".
`comparison`	No	How the total is compared with target (default ">=").

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds substantive behavior: exact enumeration vs a 100,000-sample Monte Carlo fallback, the 1,000,000-outcome enumeration threshold, that exploding dice always use Monte Carlo, and that the result carries method:"monte_carlo". This is unusually rich beyond what the structured fields provide.

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, then progressively adds enumeration/Monte Carlo detail. Dense with em-dashes but every clause earns its place; slightly long for a single sentence block.

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?

With no output schema, the description enumerates the returned fields (min, max, mean, std dev, mode, per-total probabilities, and the method label), and it discloses the estimation method and seed behavior. An agent has everything needed to call and interpret it.

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%, so the baseline is 3, but the description adds meaning: the comparison operators' effect (>=, >, <=, <, ==) on the total, and that seed only affects the Monte Carlo path and is always returned. This exceeds the schema text, though it doesn't fully re-document each param.

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 (computes the probability distribution) and resource (a dice notation), and enumerates the returned statistics. It is clearly distinguishable from the sibling roll_dice, which rolls rather than analyzes; the 'same grammar as roll_dice' phrase cements the relationship.

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?

The example 'what are the odds of 15 or more on 3d6' plus the target/comparison explanation make the intended use clear, and referencing roll_dice signals this is the analysis counterpart. It stops short of an explicit 'use roll_dice to actually roll' exclusion, so a 4 rather than 5.

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

All Dice Roller tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.