leafwiki-mcp

Overview Schema Source Related Servers Discussions Admin

move_page

Move a page to a new parent in LeafWiki by ID or path, optionally setting its position under the parent. Returns a move confirmation.

Instructions

Move a page under a new parent.

Args: id: Page identifier, preferred when both selectors are supplied. path: Slash-separated page path. parent_id: Destination parent identifier, or empty for root. position: Optional zero-based position under the parent.

Returns: Serializable move confirmation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "move_page"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No
`path`	No
`position`	No
`parent_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It mentions that parent_id empty means root and position is zero-based, but omits permissions, reversibility, side effects, conflict handling, and error behavior for a mutation tool.

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 purpose is front-loaded, and the Args section is efficient. The Returns line is redundant because an output schema already exists, preventing a perfect score.

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

Completeness3/5

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

The output schema handles return values, so that omission is acceptable. However, with no annotations, the description should also cover safety and permissions for a mutation operation; it covers parameters well but leaves behavioral context incomplete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It defines all four parameters: id as the preferred page identifier, path as a slash-separated page path, parent_id as the destination or empty for root, and position as an optional zero-based ordinal.

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: 'Move a page under a new parent.' This distinguishes the core action from most siblings, but it does not explicitly differentiate from related tools like copy_page or sort_pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose move_page over alternatives such as copy_page or sort_pages. The only contextual notes are parameter-selection details, which belong under parameter semantics rather than usage guidelines.

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