mcp-llm-wiki

Delete wiki page

wiki_delete_page

Destructive

Delete a wiki page by moving it to trash and removing it from the index. Requires explicit confirmation; check backlinks to avoid breaking links.

Instructions

Move a page to the trash (.trash//) and drop it from the index. Requires confirm=true. Check wiki_backlinks first to see if other pages link 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": {
      "path": "<path>",
      "confirm": "<confirm>"
    },
    "name": "wiki_delete_page"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path relative to the wiki root.
`confirm`	Yes	Must be explicitly true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description explains what actually happens: the page is moved to a trash location, removed from the index, and requires an explicit confirmation flag. It also warns about checking backlinks, adding meaningful behavioral context for a destructive operation.

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 a single, focused sentence that front-loads the primary behavior and adds the confirmation requirement and the backlink check. Every clause adds value with no redundancy.

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 two simple parameters, complete schema coverage, rich annotations, and clear side-effect disclosure, the description is sufficient for an agent to select and invoke the tool correctly. It covers what is destroyed, the trash location pattern, the confirmation guard, and the recommended pre-check.

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 schema already fully documents both parameters with 100% coverage. The description echoes the confirm=true requirement but does not add new semantic meaning beyond what the input schema provides, so the baseline score of 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?

The description uses a specific verb and resource: it moves a wiki page to trash and drops it from the index, clearly distinguishing deletion from siblings like wiki_move_page or wiki_update_index. The behavior is concrete and not a tautology of the tool name.

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

Usage Guidelines4/5

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

The description gives clear operational guidance: confirm=true is required and wiki_backlinks should be checked first for incoming links. It does not explicitly compare against alternative tools or state when not to use it, but the usage context and prerequisite are clear.

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

Deploy Server