D&D 5e SRD Oracle

Create Character Draft

create_character_draft

Start D&D 5e character creation by saving a new draft and receiving its draft ID, pending choices, revision, and finalization status for continued editing.

Instructions

Begin creating a character in this Play Session by storing a new draft and returning its draftId, unanswered creation choices, revision, and finalization status. Continue with fill_creation_holes, then finalize_character when ready; use discover_creation_holes to resume an existing draft. Omitting draftId creates a new draft on each call; an id already used by a draft or finalized character is rejected.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`draftId`	No	Optional caller-provided Character Draft id. Omit to let the runtime assign one. An id already used by an active draft or finalized character in this Play Session is rejected.
`playSessionId`	Yes	Play Session handle returned by create_play_session for follow-up stateful calls in the same local process or authenticated account.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Sep 21, 2026

changedInput schema / properties / draftId / description

Previous value: -"Optional caller-provided Character Draft id. Omit to let the runtime assign one."New value: +"Optional caller-provided Character Draft id. Omit to let the runtime assign one. An id already used by an active draft or finalized character in this Play Session is rejected."

First observedSep 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only state coarse hints (not read-only, not idempotent, not destructive), so the description carries the burden of behavioral disclosure. It adds key behavior: omitting draftId creates a new draft each call, duplicate ids are rejected, and the call returns creation state plus finalization status. No contradiction with annotations exists.

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 sentences deliver the core action, outputs, workflow, and idempotency nuance with no waste. The main function is front-loaded, and the workflow guidance is compact and actionable.

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 stateful creation tool, the description covers entry into the workflow, continuation steps, resume behavior, and id-reuse rules. Since an output schema exists, the description need not detail the return shape; nothing essential for correct invocation is missing.

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 coverage is 100%, so the schema already documents both parameters well. The description adds genuine value beyond the schema by explaining the behavioral consequences of omitting draftId and that an already-used id is rejected, which strengthens the agent's understanding of draftId semantics.

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: 'Begin creating a character... by storing a new draft' and names the exact outputs (draftId, unanswered creation choices, revision, finalization status). It also distinguishes itself from sibling tools like fill_creation_holes, finalize_character, and discover_creation_holes, so an agent can tell them apart without inspecting schemas.

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 an explicit workflow: continue with fill_creation_holes, then finalize_character when ready, and use discover_creation_holes to resume an existing draft. It also explains the draftId behavior and duplicate rejection, giving clear conditions for correct invocation.

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