Skip to main content
Glama
Sign In
draw.io MCP

draw.io MCP

by CycSpring
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

export_diagram

Export a local .drawio diagram to PNG, SVG, PDF, JPG, or XML format using the Draw.io desktop exporter.

Instructions

Export the current local .drawio file. .drawio copies XML; png/svg/pdf/jpg use the local Draw.io exporter.

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": {
      "path": "<path>"
    },
    "name": "export_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure. It explains format-specific export behaviors (drawio copies XML; others use local exporter). However, it omits side effects, required session state, or whether the file must already exist, 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?

Two sentences convey the essential purpose and format-specific behavior without extraneous text. Every sentence adds value, making it highly concise.

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 output schema, no annotations, and only 2 parameters with 0% schema description coverage, the description lacks critical context: prerequisites (e.g., active session), return value, error conditions, and exact file location semantics. Incomplete for an exporter tool.

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 0%, so the description must compensate. It implies 'path' refers to the current local .drawio file and mentions format alternatives, but does not specify path constraints (e.g., absolute/relative) or format implications beyond the enum. Missing details on required parameter semantics.

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 exports a local .drawio file and lists output formats. The action (export) and resource are unambiguous, but it does not differentiate from sibling tools like get_diagram or edit_diagram, which might also handle file output.

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 like get_diagram or create_new_diagram. No context about prerequisites or situations where this tool is inappropriate.

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