Skip to main content
Glama
vandewilly

MCP Dice Roller

by vandewilly

roll_dnd_stats

Generate D&D 5e character ability scores using the standard 4d6 drop lowest method for tabletop gaming character creation.

Instructions

Roll a set of D&D 5e character stats using the standard 4d6 drop lowest method.

Returns: Six ability scores rolled using 4d6, dropping the lowest die

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `roll_dnd_stats` tool in the MCP server.
    def roll_dnd_stats() -> dict:
        """
        Roll a set of D&D 5e character stats using the standard 4d6 drop lowest method.
    
        Returns:
            Six ability scores rolled using 4d6, dropping the lowest die
        """
        stats = []
    
        for _ in range(6):
            result = roll_dice("4d6kh3")
            stats.append(
                {
                    "rolls": result["rolls"],
                    "kept": result["kept"],
                    "total": result["total"],
                }
            )
    
        totals = [s["total"] for s in stats]
    
        return {
            "method": "4d6 drop lowest",
            "stats": stats,
            "totals": totals,
            "sum": sum(totals),
            "modifier_total": sum((t - 10) // 2 for t in totals),
        }
Behavior4/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the core behavioral trait (the 4d6 drop lowest mechanic) and explains the return value ('Six ability scores'). While it doesn't explicitly state safety/idempotency, the random generation nature is clearly implied by 'Roll'.

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

Conciseness5/5

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

Two sentences with zero waste: the first states the action and method, the second (labeled Returns) specifies the output format. Information is front-loaded and appropriately sized for a simple parameterless tool.

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?

Given the low complexity (no parameters, no nested objects) and absence of an output schema, the description adequately compensates by explaining the return structure ('Six ability scores'). It could optionally specify value ranges (3-18), but the 4d6 method implies this to knowledgeable users.

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?

The tool has zero parameters, establishing a baseline of 4 per the rubric. With 100% schema coverage (trivially) and no parameters to describe, no additional parameter semantics are needed in the description text.

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 uses a specific verb ('Roll') and resource ('D&D 5e character stats') and explicitly defines the method ('standard 4d6 drop lowest'). It clearly distinguishes itself from generic siblings like roll_dice or roll_multiple by specifying the exact D&D 5e character generation mechanic.

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

Usage Guidelines3/5

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

The specificity of 'D&D 5e character stats' provides implied usage context (character creation), but the description lacks explicit guidance on when to use this versus generic alternatives like roll_dice, or when not to use it (e.g., for non-D&D systems).

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/vandewilly/mcp-dice-roller'

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