LegendKeeper MCP

delete_resource

DestructiveIdempotent

Move a LegendKeeper resource and its documents to the trash; enable cascade to include child resources, and restore later using the returned ID.

Instructions

Move a resource (with its documents, and children if cascade=true) to the trash. Restore it with restore_resource using the id returned here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "<resource>"
    },
    "name": "delete_resource"
  }
}

Input Schema

Name	Required	Description
`cascade`	No	Also delete all child resources.
`confirm`	No	Must be true. Ask the user before deleting.
`project`	No	Configured project (world) name. Omit to use the default project; see list_projects.
`resource`	Yes	Resource id, or its exact name/alias (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: deletion is a move-to-trash (recoverable), cascade=true also removes child resources, and an id is returned for restoration — none of which the annotations convey.

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?

Two short sentences, zero filler, with the scope of the operation (documents, cascade children) front-loaded and the recovery path second. Every clause carries information.

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 no output schema, the description usefully tells the agent that the call returns an id consumed by restore_resource, and the annotations plus fully-documented schema cover the remaining safety and parameter needs. Nothing required to invoke it 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%, so all four parameters (including the mandatory confirm and the project defaulting rule) are already documented. The description restates the cascade effect but adds no syntax or format detail beyond 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?

States a specific verb and resource ('Move a resource ... to the trash') and clarifies the semantics of the operation — it is a soft delete, not a permanent removal. It also names the inverse sibling (restore_resource), letting an agent distinguish this from delete_document or delete_map_feature without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description routes the agent to restore_resource for undoing the action and implies reversibility, which is useful context. However, it never states when to prefer delete_resource over the many other delete_* siblings, nor any preconditions beyond what the schema's confirm field already carries.

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