Skip to main content
Glama

Create a Todrawn board

board_create

Creates an empty whiteboard, returning its ID and URL for drawing or linked handwriting projects; reports the Free plan limit when creation is blocked.

Instructions

Creates an empty whiteboard and returns its id and URL. The Free plan allows 3 boards; the error says so when the limit is hit.

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": {
      "title": "<title>"
    },
    "name": "board_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesBoard title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

With annotations already declaring non-read-only, non-idempotent, open-world behavior, the description adds real value: it discloses that the call returns an id and URL (there is no output schema) and that the Free plan caps boards at 3 with an error surfaced at the limit. It does not mention auth/login prerequisites or what state exists on failure beyond the quota case.

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?

Two sentences, both front-loaded and purposeful: the first covers action and return value, the second covers the quota constraint. Nothing is wasted.

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 one-parameter creation tool with no output schema, the description covers the essential return values and the main failure mode (plan limit). It is close to complete, with only minor omissions such as account/login context for where the board is created.

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?

There is a single required parameter, title, already documented at 100% schema coverage with a length constraint. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 ('Creates an empty whiteboard') and clarifies the result is an empty board, which separates it from board_draw, board_add, and board_read. It stops short of explicitly naming a sibling alternative, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied by the verb: an agent can infer this is the way to start a new board rather than opening an existing one. There is no explicit when-to-use or when-not-to-use guidance relative to the board_* siblings.

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