Skip to main content
Glama

Draw freehand on a Todrawn board

board_draw

Draws SVG path outlines as freehand pen strokes on a live shared whiteboard, scaling them to a chosen width and positioning them beside existing content.

Instructions

Draws freehand pen strokes from SVG path data (curves and arcs are flattened into pen lines; fills are ignored, so describe outlines). The drawing is scaled uniformly so it is width board units wide (default 400) with its top-left corner at x, y; its height follows from its shape. Think of the path coordinates as any convenient SVG coordinate system. 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. 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>",
      "paths": "<paths>"
    },
    "name": "board_draw"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoLeft edge, board units. Default 0.
yNoTop edge, board units (y grows downwards). Default 0.
pathsYes
widthNoOverall drawing width in board units, default 400.
boardIdYesBoard id (a UUID) from board_list or board_create.

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 declare it is a non-read-only, non-destructive, non-idempotent, open-world write. The description goes well beyond that by disclosing lossy rendering (arcs/curves flattened, fills dropped), the uniform scaling rule, the coordinate convention (y grows down, unbounded origin), and the collaboration effect ('Changes appear live for everyone who has the board open'). That is exactly the context an agent needs before drawing on a shared surface.

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 the verb and core behavior, and every sentence carries information (flattening, scaling, coordinate space, placement, liveness). It is a single dense paragraph with semicolon-chained clauses, which costs some scanability but wastes no words.

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 5-parameter write tool with no output schema, the description covers geometry, rendering caveats, and cooperative-editing effects well. The remaining gap is the return value: nothing states what the call yields (e.g., created element/stroke identifiers) or error behavior for invalid path data.

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 80%, yet the description still adds real meaning: `width` is a uniform scale of the whole drawing (height derives from shape) and the path coordinates may live in any convenient SVG space. That resolves the ambiguity between the top-level `width` (drawing width, default 400) and the nested per-path `width` (pen width, default 3) which the schema lists separately without contrast.

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?

States a specific verb and resource ('Draws freehand pen strokes from SVG path data') plus the rendering semantics (curves/arcs flattened to pen lines, fills ignored). This is clearly distinguishable from board_add (element insertion) and scribe_paint_image (image painting) without opening 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?

Gives explicit workflow guidance: 'Read the board first and place new content next to the current content bounds rather than on top of it.' That is a clear when/how rule and implicitly routes to board_read. It stops short of naming which sibling to use when the user wants shapes or images instead of freehand strokes.

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