holonovel

Resolve Ironsworn Moves

resolve_ironsworn

Destructive

Resolve Ironsworn actions: set or burn momentum, roll moves against two challenge dice, and mark/test progress tracks. State changes persist to the Novel, flagging uncommitted rolls.

Instructions

Resolve Ironsworn-style actions: momentum, the action-roll move framework, and progress tracks. Rolls and state changes (points, stress, momentum, progress) persist to the Novel; a roll with no following write is flagged as an uncommitted roll. move's burn replaces the action die with momentum and ignores adds; progress rank defaults to dangerous. Rolls and their state writes are recorded and are not individually reversible. Use when: setting or burning momentum, rolling a move against two challenge dice, or marking and testing a progress track. Do NOT use when: managing vows — use manage_vow (action: set).

Input Schema

TableJSON Schema

Name	Required	Description
`op`	No	Sub-operation: momentum (set, gain, lose, reset, list), progress (create, mark, test, list).
`adds`	No	Stat and bonuses added to the action die (move).
`burn`	No	Burn momentum to replace the action score (move).
`name`	No	Move name (move) or progress-track name (progress).
`rank`	No	Progress-track rank (progress).
`seed`	No	Deterministic seed (move, progress test).
`ticks`	No	Progress to mark (progress); defaults to 1.
`action`	Yes	momentum, move, or progress.
`amount`	No	Amount to set/gain/lose (momentum); defaults to 1.
`entity_id`	No	Entity or NPC id (momentum, move burn).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	No	Human-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
`status`	Yes	Machine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.3Sep 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare destructive/non-idempotent, and the description goes further: state changes persist to the Novel, a roll with no following write is flagged as uncommitted, rolls and their writes are not individually reversible, and burn semantics (replaces action die with momentum, ignores adds). That is meaningful behavioral context beyond the structured hints.

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?

Dense but front-loaded: the core purpose leads, then mechanics, then routing. Every sentence carries information, though the mechanics/constraints run together in a way that makes it slightly heavy to parse.

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 multi-mode tool with 10 parameters, 100% schema coverage, and an output schema, the description supplies what the schema cannot: persistence, irreversibility, uncommitted-roll flagging, and sibling routing. An agent can select and invoke it correctly without further information.

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 description coverage is 100%, so the baseline is 3. The description still adds semantics the schema does not carry: burn 'ignores adds' and progress rank 'defaults to dangerous'. It does not document the op sub-operations (momentum set/gain/lose/reset/list, progress create/mark/test/list), which remain schema-only.

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 (resolve) plus the concrete resources involved: momentum, the action-roll move framework, and progress tracks. It is clearly distinguishable from sibling resolvers like resolve_fate and resolve_forged, and from the manage_* state tools.

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 gives a 'Use when' list (setting/burning momentum, rolling a move against two challenge dice, marking and testing a progress track) and a 'Do NOT use when' case that routes to the named alternative manage_vow (action: set). Nothing is left to inference.

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