Skip to main content
Glama

duplicate_page

Copies an existing page by name or --index record number to create a new page, using the active session chain when source and output paths are omitted.

Instructions

按页名(或 --index 记录号)复制已有页面生成新页。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node duplicate-page.mjs source.rp output.rp sourceName newName

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": {
      "args": "<args>"
    },
    "name": "duplicate_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes
sessionNotrue 时 args 省略宿主源和输出,由当前链注入;多源工具仍传导入源。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write nature is covered. The description adds genuinely useful behavioral context—that explicit paths do not advance the session chain and that multi-source tools keep the import source. It omits whether an existing output file is overwritten and what is returned, which matters for a duplication tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded with the core action, but the middle section is dense and mixes Chinese prose, English CLI fragments, and internal references ('登记证据 gui-roundtrip', 'capabilities.md 的已验样本') that are opaque without outside context. It is compact but not streamlined.

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 two-parameter write tool with no output schema, the description covers identifier selection, session-chain injection, and the raw-args CLI layout, which is most of what an agent needs to invoke it. Missing pieces—overwrite behavior and failure modes—are secondary given annotations already mark it as a non-destructive write.

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

Parameters4/5

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

Schema coverage is only 50% and the args array is undocumented in the schema, so the description carries real weight: it gives the positional order via the CLI signature (source.rp, output.rp, sourceName, newName) and explains that args omits host source/output when session:true. That adds meaning well beyond the schema, though the relationship between args[0]/args[1] and the named parameters remains slightly implicit.

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?

Concrete verb+resource: 'duplicate an existing page by page name (or --index record number) to generate a new page'. It is clear what is copied and by what identifier. It does not distinguish itself from sibling page-creation tools such as create_blank_page or clone_library_page_content, so it falls short of a 5.

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 covers invocation modes (named call uses the session chain; raw args require session:true and omit source/output; explicit paths do not advance the chain), which is implied guidance on when each mode applies. However, it never states when to prefer this tool over siblings or what prerequisites exist (an existing project, a verified sample), leaving the agent to infer usage.

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