Skip to main content
Glama
Sign In

Umtri

by io.umtri
OverviewDiscussionsAdmin

Delete a wiki page

delete_wiki

Permanently removes a wiki page and its whole revision history — unlike an overwrite, this cannot be undone, and only the history entry (list_events) remains to say it happened. Prefer rewriting a page that went stale over deleting it: a page that records a decision you have since reversed is worth keeping with the reversal written in. Deleting is for a page that should never have existed, not for one that is out of date.

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": {
      "slug": "<slug>",
      "ref": "<ref>"
    },
    "name": "delete_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesPage slug or id.
slugYesGround slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and largely meets it: irreversibility, the fact that the entire revision history goes with the page, and the surviving audit trail in list_events. It stops short of stating permission/prerequisite requirements or what happens when the slug doesn't exist.

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 destructive consequence is front-loaded in the first clause, which is exactly right for an irreversible operation. The editorial guidance is a touch long, but each sentence carries a distinct decision rule rather than 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 two-parameter destructive tool with no annotations and no output schema, the definition covers destruction scope, irreversibility, post-deletion evidence, and usage policy. Only edge-case behavior (missing page, auth) is absent, which is minor here.

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 coverage is 100%, so the two parameters are already documented, and the description adds no extra meaning about how slug and ref combine or how ids differ from slugs. 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 ("Permanently removes a wiki page") plus the crucial scope of that removal ("and its whole revision history"), and explicitly contrasts it with an overwrite, which lets an agent separate it from edit_wiki/write_wiki without consulting schemas.

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?

Gives both sides of the decision rule: prefer rewriting a stale page, and reserve deletion for "a page that should never have existed, not for one that is out of date." The alternative is described by action rather than sibling tool name, but the when/when-not boundary is unambiguous.

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

All Umtri toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources