Dexio

move_page

Rename or move a wiki page while optionally rewriting links to it; fails if the new path already exists.

Instructions

Rename or move a page, rewriting the links to it (unless update_links is false). Fails if new_path exists.

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>",
      "new_path": "<new_path>",
      "agent": "<agent>"
    },
    "name": "move_page"
  }
}

Input Schema

Name	Required	Description
`note`	No	One line: what changed and why.
`path`	Yes
`agent`	Yes	Your own agent name (each agent sharing an API key gives its own), or the person's name if a person is making the change.
`new_path`	Yes
`workspace`	No	Another workspace: its handle, or a link into it (list_workspaces lists them). Empty: this one.
`update_links`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent operation. The description adds genuinely new behavioural context beyond that: links to the page are rewritten (with an opt-out via update_links), and the call fails when new_path already exists. It stops short of stating permission requirements or whether the move is reversible.

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?

Two compact sentences, front-loaded with the core action and followed by the two behavioural caveats. No filler; only the awkward line wrapping keeps it from being a model of brevity.

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 mutation tool with no output schema, the description covers the two facts an agent most needs: the link-rewriting side effect and the collision failure. Annotations carry the safety profile. Missing only auth/permission expectations, which is a minor gap.

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 50%; note, agent, and workspace are documented in-schema, while path and new_path are bare. The description partially compensates by explaining the effect of update_links and clarifying that path/new_path represent the current and target locations. Baseline 3 is appropriate given the mixed coverage.

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?

The description gives a specific verb pair and resource ('Rename or move a page') plus a side effect (link rewriting) and a failure condition. It is clear enough to distinguish from list/read siblings, though it never explicitly contrasts itself with edit_page or change_pages, which are the nearest neighbours.

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?

Usage is implied by the verb and the stated precondition ('Fails if new_path exists'), which tells the agent when the call will not succeed. However, there is no explicit guidance on when to prefer this over edit_page/change_pages or what prerequisites (permissions, existing source page) apply.

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

Deploy Server