Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Roll dice

dice
Read-only

Roll dice in standard notation such as 2d6+3 or 1d20, up to 100 dice of up to 1000 sides, with a cryptographic random source. Returns every roll, the modifier and the total. Use for tabletop games and simulations. Example: roll=2d6+3. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
rollNoDice notation, e.g. 2d6+3 (default 1d6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: discloses the random source ('cryptographic'), the cap on dice and sides, the exact return payload ('every roll, the modifier and the total'), and the billing model (x402 USDC or card key, first 25 free, failed calls free). The statement that repeats are not free is consistent with idempotentHint=false and 'reads or computes only and changes nothing' is consistent with readOnlyHint=true.

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 action, format and limits, and nearly every clause carries information an agent needs. The tail is slightly overpacked — pricing, card keys, free tier, failed-call policy and non-idempotency all arrive in two dense sentences, and 'each call is charged, so repeats are not free' partly restates idempotentHint=false.

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?

For a one-parameter compute tool with no output schema, the description covers input syntax, boundaries, randomness guarantees, return contents and cost — everything needed to call it correctly and judge whether the charged call is worth making. No material gap remains.

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% with a single optional parameter, so the baseline is already met, but the description still adds value by showing real notation forms and by stating limits (100 dice, 1000 sides) that the schema does not encode. Modifier syntax like '+3' is conveyed only through examples rather than explained, which keeps it off a 5.

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?

Names a specific verb+resource ('Roll dice') and immediately pins the domain with notation examples ('2d6+3 or 1d20'), hard limits ('up to 100 dice of up to 1000 sides') and the return shape. Nothing in the sibling list overlaps with dice rolling, so no disambiguation is needed and the purpose stands on its own.

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?

Gives clear intended contexts ('tabletop games and simulations') and shows a concrete invocation ('Example: roll=2d6+3'), which is enough for an agent to know when it applies. It stops short of explicit exclusions or naming a cheaper alternative for simple random picks, so it is clear context rather than full when/when-not guidance.

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.