Skip to main content
Glama
os-tack

fcp-drawio

by os-tack
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

drawio

Create and edit diagrams via high-level command strings. Automates shape, connection, style, and layout management for clear diagramming.

Instructions

Execute drawio operations. Each op string follows the FCP verb DSL.

SHAPES: add TYPE LABEL [theme:T] [near:REF dir:DIR] [at:X,Y] [size:WxH] [label:"Display Name"] remove REF | remove @SELECTOR define NAME base:TYPE [theme:T] [badge:"text"] [size:WxH]

CONNECTIONS: connect SRC ARROW TGT [label:"text"] [style:STYLE] [exit:FACE entry:FACE] disconnect SRC -> TGT

APPEARANCE: style REF [fill:#HEX] [stroke:#HEX] [font:#HEX] [fontSize:N] [bold] [italic] label REF "new text" | label SRC -> TGT "new text" badge REF "text" [pos:POSITION]

POSITION: move REF to:X,Y | to:REGION | near:REF dir:DIR resize REF to:WxH swap REF REF layout @all algo:layered|force|tree dir:TB|LR|BT|RL [spacing:N] orient TB|LR|BT|RL

ORGANIZATION: group REF REF ... as:"Group Name" ungroup "Group Name"

STRUCTURE: page add|switch|remove|list "Name" layer create|switch|show|hide|list "Name"

META: checkpoint NAME title "Diagram Title" load list | load PACK

VISUAL: export [inline|file] [fmt:png|svg|pdf] [width:N] [height:N] [page:N] [as:PATH]

NODE TYPES: box plain rectangle (generic) svc rounded rectangle (services, components) circle ellipse (states, events) decision diamond (decisions, conditions) db cylinder (databases, storage) api hexagon (apis, gateways) cloud cloud (external services) actor person shape (users, personas) doc document shape (files, reports) queue parallelogram (queues, streams) triangle triangle (warnings, deltas) process double-bordered rect (predefined processes)

THEMES (FILL / STROKE): blue #dae8fc / #6c8ebf green #d5e8d4 / #82b366 red #f8cecc / #b85450 yellow #fff2cc / #d6b656 orange #ffe6cc / #d79b00 purple #e1d5e7 / #9673a6 gray #f5f5f5 / #666666 dark #1a1a2e / #16213e (light text) white #ffffff / #000000

EDGE STYLES: solid, dashed (- - -), dotted (· · ·), animated, thick, curved, orthogonal Arrows: -> (directed), <-> (bidirectional), -- (undirected) Arrow heads: arrow, open-arrow, diamond, circle, crow-foot, none

SELECTORS: @type:TYPE, @group:NAME, @connected:REF, @recent, @recent:N, @all, @orphan, @page:NAME, @layer:NAME

RESPONSE PREFIXES:

  • shape created ~ edge created/modified

  • shape modified - shape/edge removed ! group operation @ layout/position change

CONVENTIONS:

  • Labels are unique identifiers - no ID management needed

  • Position auto-computed if omitted (near last created shape)

  • near:REF dir:DIRECTION places relative to existing shape

  • All XML structure, IDs, and geometry handled by the tool

  • Call drawio_help for full reference with examples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsYesArray of operation strings

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

With no annotations, the description thoroughly discloses behavior: it executes operations that modify diagrams, returns response prefixes indicating actions (+, ~, *, -, !, @), and handles all XML structure internally. This fully informs the agent of side effects.

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?

The description is lengthy but well-organized with clear section headings and a structured DSL. It is appropriately sized for the tool's complexity, though it could be slightly more front-loaded with a usage example.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all aspects: shapes, connections, appearance, position, organization, structure, meta, visual export, node types, themes, edge styles, selectors, response prefixes, and conventions. It is fully self-contained and compensates for the lack of output schema and annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'ops' is an array of strings, and the description provides an exhaustive DSL with syntax for shapes, connections, styling, and more. This adds immense semantic meaning beyond the schema's minimal description.

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 'Execute drawio operations' and provides a complete DSL specification, making the tool's purpose unmistakable. It distinguishes itself from siblings like drawio_help (reference) and drawio_query (query) by being the primary execution tool.

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?

The description includes a CONVENTIONS section that advises calling drawio_help for full reference, and the DSL details implicitly guide usage. However, it lacks explicit when-to-use vs when-not-to-use guidance compared to siblings, though the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/os-tack/fcp-drawio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server