D&D 5e SRD Oracle

Finalize Character

finalize_character

DestructiveIdempotent

Commit a completed character draft to a permanent in-play record, clearing the active draft and requiring Beast Stat Block ids for Druid Wild Shape selections.

Instructions

Finalize a complete supported character draft. A ready finalization stores the resulting in-play record by characterId and removes the active draft. Druid Wild Shape drafts require selected known Beast Stat Block ids.

Input Schema

TableJSON Schema

Name	Required	Description
`draftId`	Yes	Character Draft id returned by create_character_draft.
`playSessionId`	Yes	Play Session handle returned by create_play_session for follow-up stateful calls in the same local process or authenticated account.
`druidWildShapeKnownFormStatBlockIds`	No	Selected Beast Stat Block ids for a Druid Wild Shape character. Required when the finalized draft has Wild Shape.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already indicate destructive and idempotent behavior, and the description adds the exact side effects: the draft is removed and the resulting in-play record is stored. This directly discloses what gets destroyed, which is the key behavioral information an agent needs.

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?

Three tight sentences with no filler. The core action and side effect are front-loaded, and the Druid-specific requirement is placed last as a conditional addendum.

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 a complete input schema, an output schema, and annotations covering destructive/idempotent behavior, the description adds exactly the missing context: the mutation semantics and the conditional Wild Shape requirement. Nothing essential is missing for correct invocation.

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 schema already documents all parameters. The description's Druid Wild Shape note largely restates the schema's own conditional requirement and adds little semantic value beyond it.

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 names a specific verb and resource ('Finalize a complete supported character draft') and then states the concrete effect: it stores the resulting in-play record by characterId and removes the active draft. This makes the tool's function unambiguous and distinguishes it from draft-creation and session-query siblings.

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?

The description signals when to use the tool: only for a 'complete supported' and 'ready' draft. It also gives a crucial conditional for Druid Wild Shape drafts requiring Beast Stat Block ids. It does not explicitly name alternatives or state when not to use it, but the context is clear.

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