Skip to main content
Glama
Sign In
draw.io MCP

draw.io MCP

by CycSpring
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_new_diagram

Create a new diagram by providing mxGraphModel or mxfile XML, then save and open it locally in Draw.io.

Instructions

Create a new diagram from mxGraphModel or mxfile XML, save it locally, and open it in Draw.io.

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": {
      "xml": "<xml>"
    },
    "name": "create_new_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesComplete mxGraphModel or mxfile XML.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must disclose side effects. It states local saving and opening in Draw.io, which imply persistence and external interaction. However, it does not detail error cases, return values, or whether prior diagrams are affected, leaving gaps.

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 a single, well-structured sentence that immediately states the action. No filler or redundant information. Highly efficient.

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 the sibling tools (edit, get, export), the description fails to explain how the created diagram is identified or retrieved later. It omits return values (e.g., diagram ID) and whether it overwrites existing files, making it incomplete for practical use.

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?

The input schema already describes the 'xml' parameter as 'Complete mxGraphModel or mxfile XML.' The description essentially repeats this, adding no new semantic meaning beyond reinforcing the format. With 100% schema coverage, baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb (create) and resource (new diagram) along with the input format (mxGraphModel or mxfile XML). It distinguishes from sibling tools (edit, export, get) by focusing on creation.

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 lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios, or when not to use it, leaving the agent to infer from the action 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