A Model Context Protocol server for creating and manipulating Draw.IO diagrams programmatically
16 tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Most tools lack descriptions of what they return, making it difficult for LLMs to plan downstream calls. Parameter descriptions are present but often minimal (10-30 chars). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Error handling is generic. Naming is verb-first and clear, which is a strength. Average tool description ~60 chars (below 194 baseline). Many parameters lack type constraints (e.g., 'shape' in add_shape accepts free-form strings instead of enum).
Add a new shape to a diagram
Auto-arrange the layout of a diagram
Connect two shapes with an arrow
Create a new page in a diagram
Create a new empty diagram file
Delete a diagram page
Delete a shape from a diagram
No output schemas documented. Tools return generic JSON objects without specifying field names, types, or structure. LLMs cannot plan downstream calls or extract required IDs (e.g., shape_id returned by add_shape is not documented).
Missing tool annotations. All 16 tools lack readOnlyHint, destructiveHint, and idempotentHint despite clear risk levels (WRITE, DESTRUCTIVE, READ_ONLY). Agents cannot distinguish safe from dangerous operations.
Parameter 'shape' in add_shape accepts free-form strings (no enum). Should constrain to: rectangle, ellipse, diamond, parallelogram, etc. LLMs will hallucinate invalid shape names.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | <=2025-11-25 | v2 |
Generate a sample AWS VPC layout diagram
Get a diagram as a base64-encoded image
Get the details of a diagram page
Move a cell between pages in a diagram
Move a shape to a new position in the diagram
Apply style to a shape in a diagram
Update a diagram page
Update a shape's properties in a diagram
Update a shape's style properties
Parameter 'layout' in arrange_diagram lacks enum constraint. Should be: horizontal, vertical, radial (as stated in description). Free-form strings invite invalid values.
Error handling is generic ('Error: {ex.Message}'). No recovery guidance, no categorization of retryable vs fatal errors, no actionable next steps for LLMs.