cozyvtt-mcp

Character Delete

character_delete

DestructiveIdempotent

Permanently delete a character sheet you own to remove it from the campaign. Inspect the sheet first; this action cannot be undone and does not affect map tokens.

Instructions

Delete a character sheet permanently (owner only). Use character_get to inspect the sheet first and character_update to edit it; use token_delete to remove only a placed map token. This deletes the sheet itself, not just its campaign assignment. DM authority alone does not grant deletion rights. It has no undo tool and does not remove map tokens. Repeating leaves the sheet absent but may return a not-found error. Returns upstream {message} in data; REST permission and resource errors retain diagnostics. 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	Default
`character_id`	Yes	Character sheet ID owned by the authenticated user; not a map token ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Sep 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, but the description adds crucial context: the deletion is permanent with no undo, it does not remove map tokens, re-invocation may return a not-found error, and the exact success/failure response shapes are specified. This exceeds what annotations alone provide and does not contradict them.

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 longer than average, but every sentence adds necessary operational context: scope, alternatives, side effects, repeat behavior, and error contract. It is front-loaded with the core purpose and then flows logically through exclusions and return 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?

With one parameter, a rich output schema, and annotations covering safety and idempotency, the description still provides everything an agent needs: ownership requirements, no undo, no token removal, repeat behavior, and a precise success/error return contract. Nothing important 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?

The input schema already covers the single parameter at 100%, including that it must be a character sheet ID owned by the user, not a map token ID. The description reinforces this in prose but does not add substantially new parameter-level meaning beyond the schema.

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?

Opens with a specific verb and resource: 'Delete a character sheet permanently (owner only).' It clearly distinguishes itself from sibling tools by noting it is different from token_delete and character_update, so an agent can correctly identify the operation.

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?

Provides explicit when-to-use and when-not-to-use guidance, including 'use character_get to inspect the sheet first,' 'use token_delete to remove only a placed map token,' and the exclusion that 'DM authority alone does not grant deletion rights.' This fully routes the agent to the correct sibling alternatives.

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