Skip to main content
Glama

Update elements on a Todrawn board

board_update

Update existing board elements by ID with partial fields, preserving unchanged data and applying validated changes live for all viewers.

Instructions

Changes existing elements by id. Give only the fields to change; the rest of the element is kept. Fields use the same names as board_add (x, y, width, height, stroke, fill, strokeWidth, dash, label for a box, text for sticky and text elements, name/attributes/methods for a umlClass, cells for a table, points for a line or arrow, color for text and lines). Set fill or dash to null to remove it. Connectors accept routing, relation, stroke, strokeWidth, dash, fromPort and toPort; freehand strokes accept color, width and dash. An element's type cannot change. The element is read, merged and validated before anything is sent. Changes appear live for everyone who has the board open.

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>",
      "updates": "<updates>"
    },
    "name": "board_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesBoard id (a UUID) from board_list or board_create.
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate mutation, open-world behavior, non-idempotency, and non-destructiveness. The description adds substantial behavior: partial merge/keep-rest semantics, type immutability, validation before sending, null removal for fill/dash, and live visibility for collaborators.

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 core behavior is front-loaded and every sentence is relevant. The parenthetical field enumeration is dense and could be more scannable, but there is no filler.

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?

The description covers the behavior an agent needs to invoke partial updates correctly: ids, field names, merge semantics, validation, immutability of type, and live propagation. It does not clarify batch atomicity or error behavior when one of up to 200 updates fails or an id is invalid.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the schema leaves update objects mostly open via additionalProperties. The description compensates strongly by enumerating accepted field names by element type, explaining partial-update behavior, null removal, connector fields, and freehand fields.

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: 'Changes existing elements by id.' It also distinguishes this from board_add by focusing on existing elements and referencing board_add only for field naming.

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?

It clearly explains the update context: provide an element id and only the fields to change. However, it does not explicitly route the agent away from board_add for creation or board_delete for removal, and gives no explicit exclusions.

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