Skip to main content
Glama
Sign In
tldraw-mcp

tldraw-mcp

by dpunj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_flowchart

Create flowchart diagrams with auto-arranged nodes and labeled connections for visualizing processes and workflows.

Instructions

Create a flowchart diagram with nodes and connections. Nodes are auto-arranged.

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": {
      "nodes": "<nodes>"
    },
    "name": "create_flowchart"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesList of nodes
edgesNoList of connections between nodes
directionNoLayout directionvertical

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'create' implies a write operation, the description doesn't disclose important behavioral traits: whether this creates a new canvas or adds to existing content, what permissions are needed, whether the result is editable, what happens if node IDs conflict, or what the output looks like. The auto-arrangement hint is useful but insufficient for a creation 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?

The description is extremely concise at just two sentences, front-loading the core purpose. Every word earns its place with no redundancy or unnecessary elaboration. The structure moves from general creation to specific behavioral detail (auto-arrangement).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a diagram ID, image data, or success status), doesn't mention error conditions or constraints, and provides minimal behavioral context despite the tool's complexity.

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 all parameters thoroughly. The description mentions 'nodes and connections' which aligns with the schema's nodes and edges parameters, and 'auto-arranged' hints at the direction parameter's purpose. However, it doesn't add significant meaning beyond what the comprehensive schema already provides.

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?

The description clearly states the tool creates a flowchart diagram with nodes and connections, specifying that nodes are auto-arranged. It uses specific verbs ('create') and resources ('flowchart diagram'), but doesn't explicitly differentiate from sibling tools like create_shape or create_frame, which appear to be related drawing tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for creating and manipulating shapes (create_shape, create_frame, connect_shapes, etc.), there's no indication of when this flowchart-specific tool is appropriate versus more general shape tools.

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

Deploy Server

Other Tools