Skip to main content
Glama

Roll dice

roll
Read-only

Rolls dice for a Plot Speaks campaign or adventure on the server: "1d20+5", "2d6", "adv 1d20+3" (advantage), "dis 1d20" (disadvantage), "4d6 drop lowest". Returns each die and the total. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dice": "<dice>"
    },
    "name": "roll"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoWhat the roll is for, e.g. Mira's stealth check
diceYesThe roll, e.g. 1d20+5
hiddenNoTrue for a roll the story's rules keep secret from the players (a world clock, a hidden table); the result comes with a note that it is hidden and not for reading aloud

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hidden / description
      Previous value: -"True for a roll the story's rules keep secret from the players (a world clock, a hidden table); the result is for you only"New value: +"True for a roll the story's rules keep secret from the players (a world clock, a hidden table); the result comes with a note that it is hidden and not for reading aloud"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, non-idempotent and closed-world, so safety is covered. The description adds value those annotations cannot: it discloses the return shape ('each die and the total') despite no output schema, and imposes a narration-suppression behavior the agent would otherwise get wrong.

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?

Purpose and notation examples are front-loaded in one sentence, and the behavioral rule follows. The silence instruction is slightly padded by enumerating four near-identical phrases ('let me check', 'let me check on that', 'one moment', 'hang on'), which could be stated once without losing intent.

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?

With no output schema, the description correctly compensates by describing what comes back (individual dice plus total). All three parameters are documented in the schema, including the hidden-roll secrecy behavior. It omits error handling for malformed notation, the only real remaining gap for a dice roller.

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 goes beyond it by teaching the dice grammar itself — advantage ('adv 1d20+3'), disadvantage ('dis 1d20'), and keep/drop syntax ('4d6 drop lowest') — which the schema only hints at with a single '1d20+5' example.

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 and resource ('Rolls dice') scoped to a Plot Speaks campaign/adventure, and immediately grounds it with concrete notation examples ('1d20+5', '4d6 drop lowest'). No sibling tool in the list competes for this action, so an agent can select it unambiguously.

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?

Clear context for when to call it (during a campaign or adventure on the server) plus a strong delivery rule: call silently, no preamble, never mention the tool. It stops short of explicit when-not conditions, such as what to do if the notation is invalid or whether rolls should be batched.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources