Skip to main content
Glama
Sign In

Dexio

by wiki.dexio
OverviewDiscussionsAdmin

delete_page

DestructiveIdempotent

Delete a page. Its history is kept, and the result says how to restore it. permanent also deletes its history, for good, with no undo: only when the person asks; it works on a page deleted before too. Returns the pages whose links to it are now broken.

Input Schema

NameRequiredDescriptionDefault
noteNoOne line: what changed and why.
pathYes
agentYesYour own agent name (each agent sharing an API key gives its own), or the person's name if a person is making the change.
permanentNo
workspaceNoAnother workspace: its handle, or a link into it (list_workspaces lists them). Empty: this one.
base_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / permanent
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
+  "default": "",
+  "description": "Another workspace: its handle, or a link into it (list_workspaces lists them). Empty: this one.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations: annotations only say destructive=true, while the description discloses that the default keeps history, that the result explains how to restore, that `permanent` is irreversible, and that the call returns pages whose inbound links are now broken — a non-obvious side effect. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the core action, then the irreversible mode and its guardrail, then the return value. It is dense but nearly every clause carries new information; the compressed phrasing ('permanent also deletes its history, for good, with no undo') costs slight readability but not clarity.

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?

No output schema exists, and the description compensates by saying what the result contains (restore instructions, list of pages with broken links). Annotations cover idempotency and destructiveness. Minor gaps remain on conflict behavior for `base_version` and the `note`/`agent` audit parameters, but nothing that would cause an incorrect call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 50% schema coverage the baseline is 3; the description earns an upgrade by fully explaining `permanent` — the highest-risk parameter, which has no schema description at all — including its scope ('works on a page deleted before too'). It adds nothing for `note`, `base_version`, `workspace` (though workspace is described in-schema), or `path`, so it stops short of a 5.

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 ('Delete a page') and immediately disambiguates the two modes: default soft delete with retained history vs. `permanent` which erases history irreversibly. An agent can tell exactly which behavior it will get without consulting annotations.

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?

Explicitly constrains the risky path: use `permanent` 'only when the person asks', and notes it also applies to already-deleted pages, which is a genuine usage condition an agent could not infer. It does not name sibling alternatives (e.g. delete_file), but the within-tool when/when-not guidance is clear.

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

All Dexio 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