excalidraw-editor-mcp

by creativedswork

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Inspect Excalidraw canvas

inspect_canvas

Inspect a diagram canvas by fetching semantic elements, with optional document inclusion and filtering.

Instructions

Returns filtered, paginated semantic elements and optionally a small standard document.

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>",
      "canvasPath": "<canvasPath>"
    },
    "name": "inspect_canvas"
  }
}

Input Schema

Name	Required	Description
`ids`	No
`text`	No
`limit`	No
`types`	No
`cursor`	No
`canvasPath`	Yes	Full workspace-relative canvas path under projectPath, for example designs/m3/main.excalidraw. Never pass only main.excalidraw.
`projectPath`	Yes	Full workspace-relative project path, for example designs/m3.
`includeDocument`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Sep 7, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that the operation is read-oriented and returns filtered, paginated data, optionally including a standard document. However, it does not clarify side effects, output shape, or what 'small standard document' actually means.

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 one front-loaded sentence with no filler, and every word earns its place. The phrase 'small standard document' is cryptic and compresses too much meaning, which slightly reduces structural effectiveness.

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 an 8-parameter tool with no annotations and no output schema, a one-sentence description is insufficient. It omits usage context, parameter semantics, key concept definitions, and any basis for choosing among the many canvas-related sibling tools. The agent lacks enough context to call this tool reliably.

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 description coverage is only 25%, so the description must compensate for six undocumented parameters. It offers only category-level hints: 'filtered' maps roughly to ids/text/types, 'paginated' to limit/cursor, and 'optionally ... document' to includeDocument. It does not explain cursor usage, allowed types, or the meaning of the returned elements.

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 uses a specific verb ('Returns') and a clear resource ('canvas'), and 'filtered, paginated semantic elements' distinguishes it from raw canvas export or project inspection. However, terms like 'semantic elements' and 'small standard document' are unexplained, and differentiation from siblings such as open_canvas, check_canvas, and capture_canvas is only implicit.

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?

There is no guidance about when to use inspect_canvas versus alternatives like inspect_project, open_canvas, check_canvas, capture_canvas, or export_canvas. The agent must infer usage entirely from the title and sibling names.

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