D&D 5e SRD Oracle

Resolve Battle Act

resolve_battle_act

Destructive

Resolve a fully specified battle act with no pending inputs, applying its effects and resource costs to the active battle and returning any follow-up reactions or required input.

Instructions

Execute a currently available Battle act whose initialHoles is empty, using its exact subject from discover_battle_acts. This requires an active Battle with no pending fills; use fill_battle_hole for acts that require input. The operation applies the act's effects and resource costs, stores the updated Battle, and may return further required input or reactions. Do not repeat a successful call blindly; creatureFalls also accepts table-supplied reactionSpellTargetFacts.

Input Schema

TableJSON Schema

Name	Required	Description
`subject`	Yes	Copy the exact subject object returned by discover_battle_acts for an act whose initialHoles is empty. For a table-reported fall, use the creatureFalls runtime-command variant and the falling combatant id.
`playSessionId`	Yes	Play Session handle returned by create_play_session for follow-up stateful calls in the same local process or authenticated account.
`reactionSpellTargetFacts`	No	For a creatureFalls subject, provide the table's falling-creature mitigation trigger facts, including reacting combatants, procedure references, and visibility/distance witnesses. Omit when none apply; omission defaults to an empty array. Other subjects do not use this field.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Sep 21, 2026

changedInput schema / properties / reactionSpellTargetFacts / description

Previous value: -"Table-supplied falling-creature mitigation facts for the creatureFalls reaction window."New value: +"For a creatureFalls subject, provide the table's falling-creature mitigation trigger facts, including reacting combatants, procedure references, and visibility/distance witnesses. Omit when none apply; omission defaults to an empty array. Other subjects do not use this field."

changedInput schema / properties / subject / description

Previous value: -"Copy the exact subject object returned by discover_battle_acts for an act with no holes."New value: +"Copy the exact subject object returned by discover_battle_acts for an act whose initialHoles is empty. For a table-reported fall, use the creatureFalls runtime-command variant and the falling combatant id."

First observedSep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark the operation destructive and non-read-only; the description adds that the act applies effects and resource costs, stores the updated Battle, and may return further input or reactions. The 'do not repeat' warning reinforces non-idempotence with practical guidance beyond the annotations.

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?

The description is dense but compact, front-loading the core execution condition before adding prerequisites, alternatives, and warnings. Every sentence carries decision-relevant information, though the final clause about creatureFalls is slightly intricate.

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 high complexity of nested reactionSpellTargetFacts, the creatureFalls variant, and the playSessionId linkage, the description covers prerequisites, alternatives, parameter sourcing, and non-idempotency. The presence of an output schema means return-value details need not be restated.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents each parameter thoroughly. The description mostly restates schema guidance about exact subject sourcing and reactionSpellTargetFacts rather than adding substantial new parameter-level meaning.

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 states a specific verb ('Execute'), resource ('Battle act'), and condition ('initialHoles is empty'), while naming the exact source for the subject: discover_battle_acts. This clearly distinguishes the tool from fill_battle_hole and discover_battle_acts.

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 directs the agent to fill_battle_hole for acts that require input and requires an active Battle with no pending fills. The warning against blindly repeating a successful call further narrows the appropriate use case.

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