Skip to main content
Glama
PistachioPony

The Fortuneteller's Hand

Roll Defiance Dice

defy_roll

Roll up to three times to challenge a landed fortune, holding selected dice between throws to shape the result. Increase debt with each roll, then resolve the defiance.

Instructions

Roll (or re-roll) the five defiance dice, Yahtzee-style, when a player wants to fight a landed fortune from call_the_hand.

Call once to make the first roll (keep=None or []), then optionally
call again up to two more times to re-roll, keeping whichever dice the
player wants to hold between rolls. Up to three rolls total; call
defy_resolve once the player is satisfied with the dice (or after the
third roll) to lock in the result and deal debt.

keep: the die face values (1-6) to hold onto from the current dice
before rolling the rest fresh — e.g. keep=[6, 6] to hold two sixes.
Must be a subset of what's actually currently showing (raises
ValueError otherwise), and must be empty/None on the very first roll of
a ritual (there are no dice to keep yet).

Not idempotent: mutates shared dice/roll-count state across calls
within one defiance ritual; each extra roll taken also means more debt
dealt later at defy_resolve. Returns a dict with dice (sorted current
values), rolls_taken, rolls_remaining, and current_pattern/current_bend
if the dice already match a scoring pattern (three of a kind, small
straight, full house, or five of a kind — see defy_resolve).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keepNo
Behavior5/5

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

Annotations only say readOnly=false and destructiveHint=false, so the description must carry the burden. It goes well beyond that by disclosing non-idempotency, mutation of shared dice/roll-count state, extra debt consequences, and constraints such as requiring keep to be a subset of current dice.

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?

The description is detailed but efficient, front-loading the core purpose before explaining the two-phase invocation flow, parameter rules, and side effects. No sentence is filler; the repetition of 'up to three rolls' is minor and reinforces the boundary.

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?

Given the tool's moderate complexity and lack of output schema, the description covers all needed information: exact call flow, parameter constraints, state mutation effects, consequences for debt, and return value structure including dice and pattern fields. The reference to defy_resolve for scoring/enforcement also completes the ritual workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully explain keep. It does: keep holds die face values to preserve before re-rolling, must be a subset of the current showing dice, raises ValueError otherwise, and must be empty/None on the first roll. This is complete and actionable.

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 opens with a specific verb and resource: 'Roll (or re-roll) the five defiance dice, Yahtzee-style.' It clearly identifies when the tool applies ('when a player wants to fight a landed fortune from call_the_hand') and distinguishes it from the related sibling defy_resolve, which locks in the result.

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

Usage Guidelines5/5

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

The description gives explicit calling instructions: use on the first roll with keep=None, re-roll up to two more times, hold dice via keep, and call defy_resolve when satisfied. It clearly frames the tool within the larger defiance ritual and names the sibling that handles the next step.

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/PistachioPony/learnMCP'

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