Skip to main content
Glama
Sign In
moki-whiteboard

moki-whiteboard

by JKZeng-cell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

whiteboard_get_thumbnail

Read-only

Fetch the last saved whiteboard screenshot and its version to check if it is current; a thumbnail is only available after the board is opened and saved.

Instructions

Read the last saved board screenshot and its version. A thumbnail may be unavailable until the board has been opened and saved in the UI. 读取最后一次编辑保存的真实白板截图。尚未打开编辑的白板可能没有截图；返回截图版本和是否最新。

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

Input Schema

NameRequiredDescriptionDefault
boardIdNo白板 ID；省略时使用最近更新的白板，建议始终指定准确 IDdefault

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world behavior, so the bar is lower, and the description still adds real value: it warns that the thumbnail may be absent for boards never opened/saved, and states that a version and up-to-date flag come back. Return-value shape is left to the output schema, which is appropriate.

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?

The content is front-loaded and short, but every sentence is duplicated verbatim in Chinese, roughly doubling length without adding information. A single-language version would be a 5; the redundant bilingual repetition costs it points.

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 one-parameter read-only tool with an output schema, the description covers the key behavioral caveat (missing thumbnails before first save) and what is returned at a high level. Only the absence of any tie-in to sibling tools keeps it from a 5.

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 description coverage is 100%, and the single boardId parameter is fully documented in the schema (including the 'always specify an exact ID' recommendation). The description adds nothing about the parameter, so baseline 3 applies.

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: reads the last-saved board screenshot plus its version. This clearly distinguishes it from sibling tools like whiteboard_export or whiteboard_inspect, which act on live board content rather than a stored snapshot. It stops short of 5 because the 'screenshot/thumbnail' distinction is only implied.

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 gives a useful precondition ('may be unavailable until the board has been opened and saved in the UI'), which tells the agent when results can be empty. However, it never names an alternative for agents that need current board state or a full export, so selection guidance against siblings is only implied.

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