Skip to main content
Glama
Sign In
draw.io MCP

draw.io MCP

by CycSpring
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

edit_diagram

Modify a local Draw.io diagram by adding, updating, or deleting cells using their unique IDs.

Instructions

Edit the current local .drawio file by ID-based add/update/delete operations. get_diagram is recommended but not required.

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": {
      "operations": "<operations>"
    },
    "name": "edit_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden. It mentions the edit operations but fails to disclose potential side effects (e.g., file modification, saving behavior), required permissions, or error conditions.

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 compact two sentences with no filler. It front-loads the core purpose and tacks on a helpful recommendation without redundancy.

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 a mutation tool with a nested array parameter, no output schema, and no annotations, the description is insufficient. It omits workflow details (e.g., need for an existing file, persistence model, error handling) and does not clarify the expected behavior of each operation.

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 0% and the description adds little beyond the schema: it mentions ID-based and operation types, but does not explain the role of new_xml or the structure of operations array in detail. The agent must infer from the JSON schema.

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 'Edit', the resource 'local .drawio file', and the method 'ID-based add/update/delete operations'. It distinguishes itself from siblings like create_new_diagram and get_diagram.

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?

It provides a usage hint by recommending get_diagram before editing, but does not explicitly contrast with other siblings like create_new_diagram or export_diagram, nor mention when not to use.

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