cozyvtt-mcp

Character Create

character_create

Create a character sheet and register it in the current campaign roster. Use this when you need to add a new character without placing a map token.

Instructions

Create a character sheet and ensure it appears in the current campaign roster. Use character_update for an existing sheet and token_add to place a linked token; creation does not place one. Campaign gameSystem determines the initial schema; upstream validates membership and sheet data. Do not trust character_validate as a save gate. After POST, the bridge reads the roster and assigns only if not found. This is not atomic or idempotent: assignment failure returns ok=false with the created character ID in data; missing ID means creation status is unknown. Inspect the roster/UI and recover the existing sheet instead of creating a duplicate. Returns {ok:true,data} on success; tool-body failures return {ok:false,error} with optional diagnostic data. Argument-schema errors are MCP errors.

Input Schema

TableJSON Schema

Name	Required	Description
`data`	No	Optional initial sheet-field object for the campaign system, not a nested request patch; null omits it and lets upstream choose defaults.
`name`	Yes	New sheet display name, 1..200 characters; passed without trimming.
`token_image_url`	No	Optional artwork URL for the sheet; empty string omits it. This does not create a map token.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Sep 20, 2026

addedInput schema / properties / data / description

Added value: +"Optional initial sheet-field object for the campaign system, not a nested request patch; null omits it and lets upstream choose defaults."

addedInput schema / properties / name / description

Added value: +"New sheet display name, 1..200 characters; passed without trimming."

addedInput schema / properties / token_image_url / description

Added value: +"Optional artwork URL for the sheet; empty string omits it. This does not create a map token."

First observedv0.1.0Sep 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond the annotations: it discloses that the operation is not atomic or idempotent, explains the roster read-back and conditional assignment, details failure return shapes including ok=false with a created character ID, and notes when creation status is unknown. Annotations only carry high-level hints, so this behavioral detail is highly valuable.

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 front-loaded with the core purpose and each subsequent sentence provides operationally relevant information about alternatives, failure modes, and recovery. It is long, but the density of caveats is justified for a create tool with non-idempotent behavior.

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 full schema descriptions, annotations, and output schema, this description closes the remaining gaps: error contracts, non-idempotency, recovery advice, and the fact that campaign gameSystem determines the initial schema. Nothing an agent needs to invoke this tool correctly is missing.

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%, and the input schema already fully documents all three parameters: name length/trimming, data object semantics, and token_image_url default/omission. The description adds the gameSystem-dependent schema context, but parameter meaning is already carried by the schema, so the baseline 3 applies.

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 exactly what the tool does: it creates a new character sheet and ensures it appears in the current campaign roster. It explicitly contrasts with character_update for existing sheets and token_add for token placement, so an agent can distinguish this tool from its siblings immediately.

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?

It gives direct routing guidance: use character_update for existing sheets and token_add for placing a linked token, and clarifies creation does not place one. It also warns not to trust character_validate as a save gate, providing concrete when-not-to-use guidance.

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