cozyvtt-mcp

Saved Roll Delete

saved_roll_delete

DestructiveIdempotent

Delete your saved roll macro from the configured campaign. The action removes only the macro, preserving roll history; access outside your ownership returns a 404.

Instructions

Delete your Saved Roll from the configured campaign. Use saved_roll_list to identify it or saved_roll_update to change it without deletion. Any member may delete their own macro; cross-user/cross-campaign access returns 404. Destructive to the macro only, not roll history. Repeating leaves it absent but may return a not-found error; it does not roll dice. 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
`macro_id`	Yes	Saved Roll ID owned by the authenticated user in the configured campaign; other users/campaigns are inaccessible.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.0Sep 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already signal destructive and idempotent behavior, and the description adds substantial context: deletion is limited to the macro only, roll history is unaffected, repeated invocation may yield a not-found error, and no dice are rolled. No contradiction with the 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?

The description is compact and every sentence adds value: action first, then alternatives, access constraints, destructive scope, idempotency behavior, and error/response format. No filler or redundant restatement of the tool name.

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 single-parameter deletion tool with an output schema and rich annotations, the description is fully adequate. It covers prerequisites, access boundaries, side effects, retry behavior, and return shapes, leaving no operational ambiguity.

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 macro_id parameter is already documented as owned by the authenticated user in the configured campaign. The description reinforces the ownership constraint but adds little beyond the schema, so baseline 3 is appropriate.

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?

States the specific action ('Delete'), resource ('your Saved Roll'), and scope ('configured campaign'). It is clearly distinguished from the sibling update/list operations by naming the deletion action and contrasting it with saved_roll_update.

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 routes the agent to saved_roll_list for identification and saved_roll_update for alteration without deletion. It also clarifies ownership constraints, cross-user/cross-campaign 404 behavior, and repeated-deletion outcomes, giving clear when-to-use and retry guidance.

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