Skip to main content
Glama
tresor4k

macalc

calculate_dice_probability

Calculate probability of dice rolls for exact values or thresholds. Supports multiple dice, custom sides, and comparison types.

Instructions

Calculate dice roll probability for exact values, minimum or maximum targets. Returns: {probability}. See list_bundles for related 'jeux-probabilites' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_diceYesNumber of dice to roll
num_sidesNoNumber of sides on each die (default d6)
targetYesTarget value to calculate probability for
comparisonYesComparison type: exact match, at least target, or at most target

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It only states 'Returns: {probability}' without specifying format (e.g., decimal, fraction), accuracy, or performance considerations. This is insufficient for a calculation tool with potential combinatorial complexity.

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 concise—two sentences no fluff. The first sentence immediately states the action and scope, the second gives return format. It wastes no words and is well-structured.

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

Completeness3/5

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

The tool has an output schema (true), so description needn't detail return structure, but it only says 'Returns: {probability}'. For a probability calculator, this is adequate but could specify whether it's a number between 0 and 1 or a percentage. Contextual completeness is average.

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?

All four parameters have descriptions in the input schema (100% coverage). The description adds no new information beyond the schema. It repeats the comparison types, which are already defined. Baseline 3 is appropriate as schema carries the burden.

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 clearly states the tool calculates dice roll probability for exact, minimum, or maximum targets. The verb 'calculate' and resource 'dice roll probability' are specific. The mention of 'Returns: {probability}' clarifies output. It distinguishes from hundreds of siblings by focusing on dice probability.

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?

The description provides minimal guidance. It only suggests seeing list_bundles for related calculators but does not specify when to use this tool versus alternatives, nor does it mention any prerequisites or limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server