Skip to main content
Glama
Sign In
drawio-engineering-mcp

drawio-engineering-mcp

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

open_drawio_xml

Opens draw.io editor with valid XML content to view, edit, or create engineering diagrams.

Instructions

Opens the draw.io editor with a diagram from XML content. Use this to view, edit, or create diagrams in draw.io format. The XML should be valid draw.io/mxGraph XML format. IMPORTANT: Do NOT use double hyphens (--) inside XML comments, as this is invalid XML and will break the parser. Use single hyphens or rephrase instead.

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": {
      "content": "<content>"
    },
    "name": "open_drawio_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe draw.io XML content in mxGraphModel format.
lightboxNoOpen in lightbox mode (read-only view). Default: false
darkNoDark mode setting. Default: auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses that XML must be valid and warns about double hyphens. But it does not cover side effects, permissions, or behavior on invalid input beyond the comment issue.

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?

Description is brief: two sentences plus a warning note. It front-loads the purpose and adds critical usage detail concisely. No wasted words.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description covers the core action and a critical constraint. It lacks details on return behavior or editing specifics, but suffices for the complexity.

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

Parameters4/5

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

Schema coverage is 100% so baseline is 3. Description adds value by specifying the XML format requirement and the crucial hyphen rule for comments, going beyond schema descriptions.

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 'Opens the draw.io editor' and specifies the resource as 'diagram from XML content'. It explicitly mentions the format (draw.io/mxGraph XML) which distinguishes it from sibling tools like open_drawio_csv or open_drawio_mermaid.

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

Usage Guidelines4/5

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

The description says 'Use this to view, edit, or create diagrams', providing clear context. It also warns about the XML comment hyphen rule. However, it does not mention when to avoid this tool in favor of sibling 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