Skip to main content
Glama
Sign In
moki-whiteboard

moki-whiteboard

by JKZeng-cell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

新建白板页面

whiteboard_create_page

Create a new page in a specified whiteboard and set it as the current page, with expected version checks to prevent overwriting newer content.

Instructions

Create a page in an explicit board and make it the current page. 在指定白板中创建新页面，并将其设为当前页面。

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": "whiteboard_create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
boardIdNo白板 ID；省略时使用最近更新的白板，建议始终指定准确 IDdefault
expectedVersionNo先 inspect 获得版本；过期写入会返回 VERSION_CONFLICT 而不会覆盖内容

Output Schema

NameRequiredDescriptionDefault
boardNo
errorNo
boardsNo
pageIdNo
boardIdNo
currentNo
deletedNo
versionNo
alignedIdsNo
deletedIdsNo
elementIdsNo
updatedIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

B3.2/5.0
Behavior3/5

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

Adds real context beyond the annotations: creating a page also changes the current page, a side effect not captured by readOnlyHint=false / destructiveHint=false. However, it does not mention that non-idempotent repeated calls will create multiple pages, nor the VERSION_CONFLICT behavior that the schema attaches to expectedVersion.

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?

Two short sentences with the action and the resulting state up front. It loses a point only because the English and Chinese lines are full duplicates rather than the Chinese carrying extra information.

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?

An output schema exists, so return values needn't be explained, and the state change is covered. Still missing are sibling routing (manage_pages), the behavior of the undocumented 'name' parameter, and concurrency/version-conflict guidance for a mutation tool.

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 67% and the two described parameters (boardId default behavior, expectedVersion conflict semantics) are already documented in the schema, so the description adds nothing there. The 'name' parameter has no description anywhere and is not mentioned in the description, leaving a real gap.

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 ('Create a page in an explicit board') plus the resulting state change ('make it the current page'). This distinguishes it from whiteboard_create (board-level), but it does not explicitly name whiteboard_manage_pages, which is the closest sibling doing page-level operations.

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 statement of when to use this versus whiteboard_manage_pages, whiteboard_duplicate, or whether the board must already exist ('explicit board' implies a pre-existing board but doesn't say what happens if it doesn't). The only usage-adjacent signal is the implicit nudge to pass a boardId.

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