Skip to main content
Glama

write_convert

Convert a LeafWiki page into a section or a section into a page to reorganize content hierarchy without recreating the item.

Instructions

Turn a page into a section or a section into a page.

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": {
      "page": "<page>",
      "kind": "<kind>"
    },
    "name": "write_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYessection: a folder-like page for children
pageYesPage id or path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations only declare destructiveHint=false and openWorldHint=false; the description adds no behavioral context of its own. Critically, it is silent on what happens to existing child pages when a section is converted back into a page, and on reversibility or required permissions.

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?

A single well-formed sentence with the action and both transformation directions front-loaded, no filler. Its brevity is close to under-specification, but nothing is redundant.

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?

With two fully documented parameters and no output schema, the structural coverage is adequate. For a mutation tool with thin annotations, however, the missing disclosure about child-page side effects and failure conditions leaves a real 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 100%, including an enum note explaining that 'section' is a folder-like page for children, so the baseline is 3. The description's directional framing loosely maps to the 'kind' enum but contributes no format or edge-case detail beyond the schema.

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?

A specific verb ('turn ... into') plus both directions of the resource transformation (page <-> section), which is more than a restatement of 'convert'. It does not name or distinguish itself from plausible siblings like write_update_page or write_move, so an agent must infer the boundary.

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 bidirectional phrasing implies when the tool applies, but there is no explicit when-to-use versus write_update_page/write_move, and no statement of preconditions such as whether the page must be empty or may already contain children.

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