Skip to main content
Glama
Sign In
The Fortuneteller's Hand

The Fortuneteller's Hand

by PistachioPony
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Resolve Defiance

defy_resolve

Finalize the defiance ritual: lock in current dice, add one debt card per roll taken, and reset state for a new roll.

Instructions

Lock in the current defiance dice as final, deal debt, and reset the ritual.

Call once, after defy_roll has been called at least once and the
player is done rolling (whether by choice or because three rolls were
taken). Ends the current defiance ritual — a subsequent defy_roll call
starts a fresh one from scratch.

Takes no parameters. Raises ValueError if called before any defy_roll
in this ritual. Not idempotent: mutates the shared debt row, adding
one debt card per roll taken during the ritual (more rolls, more debt,
win or lose), and clears the ritual's dice/roll-count state. Returns a
dict with final_dice, rolls_taken, pattern and bend (None if no
scoring pattern was hit — otherwise three of a kind/"turn the blade",
small straight/"stay the hand", full house/"take the cup", or five of
a kind/"seize the pen"), and debt_dealt (the cards just added to the
debt row).

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": "defy_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Despite annotations (readOnlyHint=false, destructiveHint=false), the description greatly extends transparency: it warns about a ValueError if called prematurely, declares it non-idempotent, details that it adds one debt card per roll taken (win or lose), and resets dice/roll-count state. It also fully explains return fields, including pattern meanings.

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 well-structured: a single-sentence summary first, then clear usage prerequisites, then a detailed behavior/return spec. Every sentence adds value, and the length is justified by the tool's complexity (state mutation, error handling, and a rich return value).

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?

With no output schema, the description fully explains the return dict (final_dice, rolls_taken, pattern, bend, debt_dealt) and the pattern value mappings. It covers the error condition, state mutation, and the ritual lifecycle, making it complete for the tool's complexity.

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, and the schema is an empty object. The description explicitly states 'Takes no parameters,' and no further parameter guidance is needed. Per the rubric, a baseline of 4 applies for zero-parameter tools, and the description does not add parameter-specific meaning beyond that.

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 precise action: 'Lock in the current defiance dice as final, deal debt, and reset the ritual.' It clearly distinguishes from siblings like defy_roll (the preceding step) and call_the_hand, making the purpose unambiguous.

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?

Explicitly specifies when to call: after defy_roll has been used at least once and rolling is done (whether by choice or after three rolls). It also notes that a subsequent defy_roll starts a fresh ritual, providing clear sequencing.

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

Deploy Server

Other Tools