moki-whiteboard

by JKZeng-cell

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

列出 MOKI 白板

whiteboard_list

Read-only

Lists available local whiteboards to help agents select an explicit boardId before inspecting or editing content.

Instructions

List local whiteboards. Start here to choose an explicit boardId before inspecting or editing. 列出可供 Agent 操作的所有白板文档。

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_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description's 'local whiteboards' is consistent with the closed-world hint and adds a small amount of context. It says nothing about ordering, size, or pagination of the listing, and with an output schema present that gap is minor rather than severe.

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 guidance is front-loaded and every sentence carries information. The bilingual restatement of the same content is redundant for an English-reading agent, which is the only thing keeping it from a 5.

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

Completeness5/5

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

This is a zero-parameter list tool with a declared output schema and read-only annotations, so return values and safety need no prose. The description covers what it returns, why to call it first, and how its output feeds downstream tools – nothing an agent needs is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description does add forward-looking meaning by naming boardId as the value the agent should extract from the result, which is useful even though it is not an input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (list local whiteboards) and immediately positions the tool in a workflow: 'Start here to choose an explicit boardId before inspecting or editing.' That distinguishes it from the inspect/edit siblings without requiring the agent to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Start here to choose an explicit boardId before inspecting or editing' gives explicit when-to-use guidance and implicitly steers the agent away from jumping straight to edit tools. It stops short of naming a specific alternative or listing exclusions, so it is clear context rather than a full routing rule.

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

Deploy Server