Skip to main content
Glama
Sign In
excalidraw-editor-mcp

excalidraw-editor-mcp

by creativedswork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Excalidraw project

create_project

Create a managed project and open its default canvas to start diagramming.

Instructions

Creates a managed project and opens its default canvas.

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": {
      "projectPath": "<projectPath>",
      "name": "<name>",
      "mutationId": "<mutationId>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
mutationIdYes
projectPathYesFull workspace-relative project path, for example designs/m3.
defaultCanvasPathNoCanvas path relative to projectPath, for example main.excalidraw.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal one side effect (opening the default canvas), but it is silent on whether creation is idempotent, what happens if the project path already exists, what 'managed' entails, and what permissions or side effects accompany creation. The required 'mutationId' parameter strongly suggests idempotency semantics, yet the description never mentions it.

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?

The description is a single front-loaded sentence with zero filler, which earns high marks for conciseness. However, at only eight words it is undersized relative to the tool's complexity (four parameters, no annotations, no output schema), so it is not fully 'appropriately sized.'

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?

Given no annotations and no output schema, the description must carry more weight than it does. It omits the return value, error behavior on existing paths, whether the default canvas is created or merely opened, and the purpose of mutationId. For a mutation tool in a rich domain with 24 siblings, this is a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, so the description must compensate for the undocumented 'name' and 'mutationId' parameters. It does not: it only loosely echoes 'defaultCanvasPath' via 'opens its default canvas,' and gives no meaning for the required idempotency key or the meaning of 'name' (display name versus path basename).

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 states a specific verb ('Creates') and resource ('managed project'), and adds the secondary behavior 'opens its default canvas,' which distinguishes it from open_project and create_canvas. The term 'managed' is unexplained but does not obscure the core purpose. It falls short of a 5 because it does not explicitly contrast with sibling 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?

No guidance is given on when to use this tool versus siblings such as create_canvas or open_project. The description never states conditions, exclusions, or which alternative should be chosen instead, leaving the agent to infer selection from the tool name alone.

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