Skip to main content
Glama

write_copy

Copy a LeafWiki page with its content, tags, properties, and files to a new title under a parent; omit the parent to place it at the top level.

Instructions

Copy a page (content, tags, properties, files) under a parent with a new title.

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>",
      "title": "<title>"
    },
    "name": "write_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
slugNoURL segment; omit to derive it from the title
titleYes
parentNoParent id or path; omit for the top level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare destructiveHint=false and openWorldHint=false, so the profile is partially covered. The description adds useful scope detail (that tags, properties and files come along) but does not disclose return value, slug-collision behavior, or effect on any existing target.

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 front-loaded sentence that efficiently communicates purpose and copied content. No filler, though it could be slightly more explicit about inputs.

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?

For a simple 4-parameter copy tool with no output schema, the description covers purpose and copy scope but leaves gaps around the return value and the required page/title semantics.

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 coverage is 75%, with the two required params (page, title) carrying no schema description. The description compensates by clarifying that 'title' is the new title of the copy and 'page' is the source, though it adds nothing about slug or parent beyond the schema's own notes.

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 (copy), resource (page), and enumerates what is carried over (content, tags, properties, files), plus placement under a parent with a new title. This distinguishes it from create/move siblings, though no sibling is named explicitly.

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?

The description implies copying but gives no when-to-use vs alternatives guidance, no prerequisites, and no exclusions. An agent must infer that it should choose this over write_create_page or write_move.

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