Dice MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: clear_history manages session history, get_history retrieves it, reroll repeats the last roll, roll_dice handles standard dice notation, and roll_pool focuses on pool-based systems. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs (clear, get, reroll, roll) and specific nouns (history, dice, pool). The naming is uniform and predictable across all five tools.
With 5 tools, this server is well-scoped for dice rolling and session management. Each tool serves a distinct and necessary function, covering core operations without bloat or redundancy.
The toolset provides complete coverage for dice rolling domains: session history management (clear and get), roll repetition (reroll), standard dice mechanics (roll_dice), and pool-based systems (roll_pool). There are no obvious gaps for typical TRPG or dice-based workflows.