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

drawio-engineering-mcp

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

markup_schematic

Overlay engineering annotations on schematic screenshots to mark proposed changes, issues, or review comments.

Instructions

Opens a schematic screenshot in draw.io with engineering annotations overlaid. The original image becomes a locked background layer. Annotations (redline circles, revision clouds, delta callouts, arrows, text notes) are placed on a foreground layer. Use this to mark up existing schematics with proposed changes, issues, or review comments. Claude can analyze a screenshot with vision first, then call this tool with coordinates and descriptions for each annotation.

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": {
      "image_path": "<image_path>",
      "annotations": "<annotations>"
    },
    "name": "markup_schematic"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_pathYesAbsolute path to the schematic image file (PNG, JPG, etc.)
annotationsYesArray of annotations to overlay on the schematic
titleNoOptional title for the markup diagram
image_widthNoDisplay width of the image in pixels. Default: 800
image_heightNoDisplay height of the image in pixels. Default: 600

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Describes the locked background layer and foreground annotations, but lacks details on file handling, saving behavior, or limitations. No annotations are provided, so description carries full burden.

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?

Four sentences, front-loaded with key action, each sentence adds value. Could be slightly shorter but is well-structured and efficient.

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?

Covers workflow (vision first), layering, use case, and annotation types. Omits some behavioral details but is adequate given absence of output schema and annotations.

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?

Schema coverage is 100%, meeting baseline. Description adds no extra meaning beyond what the schema provides for parameters, such as defaults for w, h, color.

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 specifies 'opens a schematic screenshot in draw.io with engineering annotations' and lists annotation types, clearly distinguishing it from sibling tools like open_drawio_engineering 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?

Explicitly states 'Use this to mark up existing schematics' and suggests analyzing with vision first, providing clear context though not explicitly excluding alternatives.

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