Skip to main content
Glama

Drawbridge Network Diagrams

export

Render a Drawbridge/draw.io network diagram to an output format (svg, png, drawio, dot, csv, netbox.csv, netbox-devices.csv, describe.json, clab.yml). Returns the exported content. CHOOSING kind: drawio when the user will open or edit the drawing (this is usually what they want, and it is the only one they can change); svg to embed in a document or a page; png to show inline in a chat; describe.json to READ a drawing back and reason about it; csv / netbox.csv for a cable schedule and netbox-devices.csv for the hardware; dot to hand the topology on; clab.yml to turn the design into a Containerlab topology you can deploy. Results carry name: a suggested basename for this diagram. Write every file for one diagram into its own directory named after it — /.drawio, /.svg, /.cables.csv — so two diagrams never share a directory.

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": {
      "document": "<document>"
    },
    "name": "export"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOutput format. Defaults to svg.
nameNoBasename to use for this diagram instead of the one derived from its content. Slugified; wins over the document’s own name.
themeNoRender theme. Omit to follow the OS appearance; pin it for machine-independent output.
documentYesThe .drawio document as XML text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does useful work: it discloses that the tool returns the exported content (implying the caller writes files), that results carry a `name` basename, and it prescribes a per-diagram directory convention to prevent collisions. It does not state permission requirements, whether the operation is read-only, or failure behavior for invalid documents.

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?

Front-loaded with verb, resource, and format list before the longer selection guidance, and every sentence carries actionable content. The single dense paragraph is long, and the kind-selection material could be broken into a list for faster scanning, but there is no filler.

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?

For a four-parameter render tool with no output schema and no annotations, the description covers what it does, how to pick each output format, what comes back, and how to handle returned filenames. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning beyond the enum list by explaining each `kind` value's purpose and by clarifying that `name` is a suggested basename that overrides the content-derived name. `theme` and `document` are left entirely to the 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?

Opens with a specific verb and resource: 'Render a Drawbridge/draw.io network diagram to an output format', then enumerates every supported format. An agent can immediately tell this is the rendering/export tool rather than create_diagram, edit_diagram, or validate.

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 'CHOOSING kind' block gives an explicit scenario-to-format mapping (drawio for editing, svg for embedding, png for inline chat, describe.json to read back, csv/netbox.csv for cable schedules, clab.yml to deploy), which is exactly the decision an agent must make. It stops short of stating when to prefer this tool over siblings like describe or edit_diagram at the tool level.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources