livediagram

Add a Plan board

add_board

Put a Plan board on a tab in Plan (any other tab is refused): a preset (kanban, todo, sprint, bug-triage, retro, roadmap, weekly...) or columns by name, placed beside what the tab holds. A column named like one the document already has shares it, so its cards show on both. Then add cards with change_items.

Input Schema

TableJSON Schema

Name	Required	Description
`tabId`	No	The tab to put it on, which must be in Plan; defaults to the first tab with a board, else the first tab.
`title`	No	The board’s title.
`types`	No	The card types it shows and takes, by name or id; an empty list takes none. Absent: the preset’s (todo takes Actions, roadmap Projects, sprint Stories, Tasks and Bugs...; the answer says), or every type for columns by name. A preset’s Bug or Story the document lacks is added to its card types.
`preset`	No	A ready-made board: its columns, card fields and widgets. Defaults to kanban (blank with columns).
`columns`	No	Column names, left to right, replacing the preset’s. A name the document’s boards already use shares their column, so its cards show here too.
`documentId`	Yes	The document (from find_documents).

Output Schema

TableJSON Schema

Name	Required	Description
`rev`	Yes	The tab revision after it.
`url`	Yes	Link that opens the document in the livediagram editor.
`tabId`	Yes	The tab it was put on.
`takes`	Yes	The card types it shows: a card of another type is saved but no board shows it.
`title`	Yes	The board’s title.
`brought`	Yes	Card types the board brought into the document, by name (a bug-triage board brings Bug when the document lacks it); empty when it had them all.
`columns`	Yes	Its columns, left to right.
`elementId`	Yes	The board element id.
`changesetId`	Yes	The changeset that added it (revertible).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / tabId / description

Previous value: -"The tab to put it on; defaults to the first tab with a board, else the first tab."New value: +"The tab to put it on, which must be in Plan; defaults to the first tab with a board, else the first tab."

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / types / description

Previous value: -"The card types it shows and takes, by name or id. Absent: the preset’s (todo takes Actions, roadmap Projects, sprint Stories, Tasks and Bugs...; the answer says), or every type for columns by name. A preset’s Bug or Story the document lacks is added to its card types."New value: +"The card types it shows and takes, by name or id; an empty list takes none. Absent: the preset’s (todo takes Actions, roadmap Projects, sprint Stories, Tasks and Bugs...; the answer says), or every type for columns by name. A preset’s Bug or Story the document lacks is added to its card types."

Changed3 schema fields changedOct 9, 2026

changedInput schema / properties / types / description

Previous value: -"The card types it shows and takes, by name or id. Absent: the preset’s (todo takes Actions, roadmap Projects...; the answer says), or every type for columns by name."New value: +"The card types it shows and takes, by name or id. Absent: the preset’s (todo takes Actions, roadmap Projects, sprint Stories, Tasks and Bugs...; the answer says), or every type for columns by name. A preset’s Bug or Story the document lacks is added to its card types."

addedOutput schema / properties / brought

Added value: +{
+  "description": "Card types the board brought into the document, by name (a bug-triage board brings Bug when the document lacks it); empty when it had them all.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "tabId",
-  "elementId",
-  "title",
-  "columns",
-  "takes",
-  "changesetId",
-  "rev",
-  "url"
-]New value: +[
+  "tabId",
+  "elementId",
+  "title",
+  "columns",
+  "takes",
+  "brought",
+  "changesetId",
+  "rev",
+  "url"
+]

AddedOct 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, closed-world), so the bar is lower. The description still adds real behavioral context: the tab-refusal rule and the non-obvious side effect that a column sharing a name with an existing one makes cards appear on both boards.

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?

Three tightly packed sentences, front-loaded with the action and its hard constraint, with no filler. The parenthetical preset list and the change_items hand-off both earn their place.

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?

An output schema exists so return values need not be explained, and annotations cover safety. The description supplies the creation constraints and the column-sharing side effect, leaving little an agent needs missing, though the default preset behavior is only in the schema.

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 description coverage is 100%, so the schema already documents every parameter including presets, columns, and types. The description restates the preset/columns choice and the sharing behavior, adding little beyond what the schema provides; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Put a Plan board on a tab in Plan') and immediately scopes it with a hard constraint ('any other tab is refused'). An agent can distinguish this from add_tab/add_form/add_sheet, though no sibling is named by contrast.

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 a clear precondition (the tab must be in Plan, otherwise it is refused) and routes card creation to a named alternative ('Then add cards with change_items'). No explicit when-not scenario beyond the tab constraint, but usage is well-framed.

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

All livediagram tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?