Skip to main content
Glama

Connect elements on a Todrawn board

board_connect

Connect existing board elements by ID with persistent connectors that stay attached when elements move; set ports, routing, styles, and UML relationships.

Instructions

Draws connectors between existing elements by id; they stay attached when the elements move. Connectors attach to box, sticky and umlClass elements only (use an arrow element between other shapes, or give a free point {x, y} as an end). Ports default to the sides that face each other. relation gives UML arrowheads (inheritance, aggregation, composition, dependency). A connector cannot carry a label; to caption one, add a text element near it with board_add. The board is read first to check the ids exist. 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>",
      "connections": "<connections>"
    },
    "name": "board_connect"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds real behavioral context on top: existing ids are validated against a board read first, and changes propagate live to collaborators. It stops short of saying what happens when an id is invalid or that repeated calls create duplicate connectors (consistent with idempotentHint=false), leaving a modest gap for a mutating tool.

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?

Dense but purposeful: capability, anchor constraints, fallback, defaults, UML semantics, labeling caveat, and validation/side effects each get one short clause with no repetition. Front-loaded with the core verb and resource.

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 batch mutation tool with no output schema, the description covers attachment behavior, allowed element types, defaults, id validation and live collaboration, which is enough to call it confidently. The missing piece is what a successful call returns (e.g., connector ids) and the failure mode for unknown ids.

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 coverage is roughly 50%, and the description largely restates what the schema already documents (from/to as ids or free points, port defaults facing each other, relation as UML arrowheads). It never explains the undocumented fields such as dash or the strokeWidth default, so it neither compensates for the coverage gap nor adds much 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?

States a concrete verb and resource ("Draws connectors between existing elements by id") plus the key persistence property that they stay attached when elements move. The allowed anchor types (box, sticky, umlClass) further pin down what it operates on, distinguishing it from element-creating siblings like board_add or board_draw.

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 says what to do when the target shape is not a box/sticky/umlClass ("use an arrow element between other shapes, or give a free point {x, y}"), and redirects captioning to board_add when a label is needed. These are concrete when-not conditions with named alternatives rather than vague hints.

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