Skip to main content
Glama

Add elements to a Todrawn board

board_add

Add shapes, sticky notes, text, lines, arrows, tables and UML classes to a board from simple element specs, filling in board defaults. Returns new element ids so you can link them with connectors.

Instructions

Adds shapes, sticky notes, text, lines, arrows, tables and UML classes to a board. Each element is a simple spec with a type; everything not given gets the board's normal defaults. Typical sizes: shapes and boxes 180 x 96, sticky notes 180 x 180, tables 3 x 3 cells (96 wide columns), UML classes 240 wide, body text 18. Pick colours as #rrggbb; the default ink adapts to a light or dark board. Returns the new element ids; use board_connect to link boxes, notes and classes. Coordinates are board units (about one screen pixel at 100% zoom); x grows right and y grows DOWN, the origin is arbitrary and boards are unbounded. Read the board first and place new content next to the current content bounds rather than on top of it. Leave about 40 units between elements. For freehand drawings use board_draw. 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>",
      "elements": "<elements>"
    },
    "name": "board_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesBoard id (a UUID) from board_list or board_create.
elementsYesElements to add, in drawing order (later ones draw on top).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false; the description adds context beyond them: omitted fields get board defaults, new element ids are returned, and 'Changes appear live for everyone who has the board open' — a real collaborative side effect an agent should know about. It stops short of warning that repeated identical calls create duplicates (relevant given idempotentHint=false) or noting any element-count limits.

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?

Front-loaded with what it does, then defaults, then coordinate/placement rules, then a pointer to board_draw. It is a dense single paragraph with no filler sentences, though the typical-size and colour-format details could be trimmed or structured into a list for faster scanning.

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?

For a tool with 12 element variants and no output schema, the description covers the essentials: return value (new element ids), coordinate semantics, default-filling behaviour, placement/spacing rules, and real-time visibility to collaborators. Nothing an agent needs to call it correctly 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?

Schema coverage is 100% and the schema already documents per-type defaults, so the bar is higher than baseline. The description still adds real meaning: the coordinate system (board units ≈ screen pixel at 100% zoom, y grows DOWN, arbitrary origin, unbounded board) and typical sizes per element type, which the schema alone does not convey as a convention.

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?

Opens with a specific verb and resource — 'Adds shapes, sticky notes, text, lines, arrows, tables and UML classes to a board' — enumerating exactly the element kinds it accepts. It also distinguishes itself from siblings by naming board_draw for freehand work and board_connect for linking.

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

Usage Guidelines5/5

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

Explicitly routes alternatives: 'For freehand drawings use board_draw' and 'use board_connect to link boxes, notes and classes'. It also gives positive workflow guidance — read the board first, place next to current content bounds rather than on top, leave ~40 units between elements.

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