Skip to main content
Glama

Delete record

wiki_del
Destructive

Delete one data record. Read it first to verify the target. Records do not have page revision history, and deletion has no version guard.

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>",
      "key": "<key>",
      "org": "<org>"
    },
    "name": "wiki_del"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe record's key on a keyed page, or its _id on an unkeyed page.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description doesn't need to restate risk; instead it adds genuinely new behavior: records lack page revision history and deletion has no version guard, meaning there is no undo or conflict protection. That directly changes how an agent should pre-verify. It stops short of saying what a successful deletion returns or how a missing key is handled.

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?

Three short sentences, each carrying a distinct load: the action, the required verification step, and the irreversibility caveat. Front-loaded with the operation and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, three-required-parameter tool with no output schema, the definition covers the two things that matter most — verify before deleting and the absence of any rollback/version guard. Minor gaps remain around error behavior for a nonexistent key and confirmation of what returns, but nothing essential to calling 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% and every parameter is documented in-schema (path format, key semantics, required org slug), so baseline is 3. The description adds nothing about path/key/org beyond 'one data record', so it neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus cardinality: 'Delete one data record.' An agent can tell exactly what operation is performed, though the text never differentiates this from the similarly named wiki_remove sibling, leaving that distinction to inference.

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?

Gives one concrete procedural prerequisite — 'Read it first to verify the target' — which is real when-to-use guidance for a destructive call. It offers no when-not guidance and no explicit alternative tool, so the guidance is partial rather than complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources