Skip to main content
Glama
Sign In
drawio-mcp

drawio-mcp

by rifujin123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

draw_sequence_diagram

Generate a UML sequence diagram by defining participants and ordered messages; the tool outputs a .drawio file ready for use in diagrams.net.

Instructions

Create a UML sequence diagram as a .drawio file. Accepts participants (actor, boundary, control, entity, lifeline) and messages (synchronous, asynchronous, return, create, destroy) ordered chronologically. Output is a .drawio file that opens in draw.io (diagrams.net).

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": {
      "participants": "<participants>",
      "messages": "<messages>"
    },
    "name": "draw_sequence_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoSequence Diagram
messagesYes
participantsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It explains the input and output format but omits details about side effects, idempotency, or permission requirements, which leaves some behavioral aspects unclear.

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 two concise sentences, front-loading the main purpose and immediately detailing accepted types, with 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 complexity of creating a diagram, the description covers the core inputs and output format well. However, it lacks information on where the .drawio file is saved or returned, and does not mention error conditions or constraints.

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?

The schema has 0% description coverage, yet the description lists participant and message types and their ordering, adding significant meaning beyond the raw schema. It explains the structure of participants and messages, but misses the 'title' parameter.

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 tool creates a UML sequence diagram as a .drawio file, listing specific participant types and message types, which distinguishes it from sibling tools like draw_class_diagram or draw_activity_diagram.

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

Usage Guidelines3/5

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

The description implies usage for creating sequence diagrams but does not explicitly guide when to prefer this tool over alternatives like draw_class_diagram or provide exclusions or prerequisites.

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