Skip to main content
Glama
gwmage

Rootr MCP Server

Update a Rootr whiteboard (replace the scene, or config/icon)

rootr_update_whiteboard

Merge-patch whiteboard config/icon or replace entire scene. Read existing board first to preserve shapes and edges.

Instructions

Merge-patch a Rootr (루터) WHITEBOARD: update config/icon, or REPLACE THE WHOLE scene (if you pass scene, it replaces every existing shape/edge — call rootr_read_whiteboard first and resend the shapes/edges you want to keep so you don't lose existing content). Authoring guide: a scene is { shapes: [{id,type,x,y,w,h,text?,style?}], edges: [{id,from,to,label?}] } — shapes are the nodes of a lightweight diagram (flow diagrams, brainstorming, journey maps), edges connect them by id. Meaning must live in shape/edge TEXT (text/label) — that is what gets indexed into the knowledge graph; x/y/w/h and style are visual-only layout. Read the board first (rootr_read_whiteboard) before updating so you know the existing shape ids edges refer to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoEmoji icon for the node
sceneNoCOMPLETE scene to set — omitted existing shapes/edges will be dropped
configNoFree-form whiteboard config object
whiteboardIdYesWHITEBOARD node id
Behavior1/5

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

The description states that passing 'scene' replaces every existing shape/edge, which is destructive behavior. However, annotations have destructiveHint: false, contradicting the description. This is a serious inconsistency.

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

Conciseness5/5

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

The description is well-structured and concise. The first sentence states the action, followed by critical usage warning, then detailed parameter guide. Every sentence serves a purpose without redundancy.

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?

Given the complexity (nested objects, no output schema), the description covers purpose, usage, parameter details, and behavioral impact. It could mention what the response looks like, but overall it's adequately complete.

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 100%, but the description adds meaningful context: it explains that scene replaces all content, provides an authoring guide for shapes and edges, and clarifies that text/label is indexed in knowledge graph while x/y/w/h/style are visual-only. This adds value beyond the schema.

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 clearly states the tool's purpose: merge-patch a whiteboard, updating config/icon or replacing the whole scene. It distinguishes from siblings like rootr_read_whiteboard and rootr_create_whiteboard, and provides specific verb-resource pair.

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?

The description explicitly advises to read the board first before updating to avoid losing content, and explains when to use scene replacement. It lacks explicit 'when not to use' but provides strong contextual guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gwmage/rootr-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server