Skip to main content
Glama
Sign In
mcp-llm-wiki

mcp-llm-wiki

by RickyKleinhempel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move page or folder

wiki_move_page
Destructive

Move or rename wiki pages or folders and automatically rewrite relative Markdown links, keeping wikilinks intact. Preview planned changes with dry-run.

Instructions

Move or rename a page or a whole folder and rewrite relative Markdown links (id-based wikilinks stay valid). With dryRun=true you get the planned changes without writing anything.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "wiki_move_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget path relative to the wiki root.
fromYesCurrent path (file or folder) relative to the wiki root.
dryRunNoPlan only, do not write.
overwriteNoOverwrite an existing target (default false).
updateLinksNoRewrite links on other pages (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

The destructiveHint annotation already flags mutating behavior, and the description adds meaningful behavioral detail: relative Markdown links are rewritten, id-based wikilinks remain valid, and dryRun produces no writes. This is useful transparency beyond the structured annotation and schema.

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 two tight sentences with no filler. The core operation is front-loaded, the link-rewriting behavior is stated in the first sentence, and the dryRun capability is a useful second sentence.

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 move/rename tool with a destructive annotation and a full schema, the description covers the main behavior, link handling, and dry-run planning. It does not describe return values or error behavior, but there is no output schema to satisfy and the core invocation context is sufficiently complete.

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%, so parameters are already well documented. The description reinforces the meaning of dryRun and provides context about link rewriting, but it does not add significant new semantic detail beyond the schema for from, to, overwrite, or updateLinks.

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 states a specific action (move or rename) on a specific resource (page or folder), and adds the key side effect of rewriting relative Markdown links while id-based wikilinks remain valid. This clearly distinguishes it from sibling write, patch, and delete tools.

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?

The description implicitly communicates when to use this tool: when a page or folder needs to be moved or renamed, with dryRun optionally used for planning. However, it does not explicitly state when not to use it or name alternative tools for content editing or deletion, leaving usage guidance mostly inferred.

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

Deploy Server

Other Tools