moki-whiteboard

Overview Schema Source Related Servers Discussions Admin

whiteboard_duplicate

Duplicate all pages and content of a whiteboard while preserving image and file references, so you can create a copy without losing linked assets.

Instructions

Duplicate all pages and content of a board, preserving image and file references. 复制白板的全部页面与内容；图片和文件引用保留。

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": {
      "boardId": "<boardId>",
      "title": "<title>"
    },
    "name": "whiteboard_duplicate"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`boardId`	Yes
`expectedVersion`	No

Output Schema

Name	Required	Description	Default
`board`	No
`error`	No
`boards`	No
`pageId`	No
`boardId`	No
`current`	No
`deleted`	No
`version`	No
`alignedIds`	No
`deletedIds`	No
`elementIds`	No
`updatedIds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Oct 21, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is known. The description adds useful context that all pages and content are copied and that image/file references are preserved, but it does not explain whether the original board is left untouched or whether permissions/links are shared versus cloned.

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 English sentence is front-loaded and wastes no words. The Chinese translation is a direct restatement rather than added substance, but the overall definition remains very short and easy to scan.

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

Completeness2/5

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

The output schema exists, so return values need not be described, and annotations cover safety. However, with zero parameter documentation and no guidance on how duplication differs from whiteboard_create, the description leaves too much unresolved for a three-parameter mutation tool.

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

Parameters2/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 for three undocumented parameters. It mentions neither boardId, title, nor expectedVersion, leaving the agent to guess that boardId is the source and title is the new board title, and to figure out expectedVersion without any help.

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?

The description gives a specific verb and resource: 'Duplicate all pages and content of a board.' It is clear this creates a copy rather than creating a fresh board or renaming one, though it never explicitly names the sibling create/rename tools as alternatives.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as whiteboard_create. The agent must infer the use case entirely from the single sentence about duplication.

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

Deploy Server