Skip to main content
Glama

Drawbridge Network Diagrams

create_diagram

Generate a routed, laid-out network diagram from topology text (Graphviz DOT, Mermaid, CSV, CDP/LLDP neighbour output from most switch vendors, a FortiLink topology dump, Containerlab, Meraki or UniFi JSON, or an Ansible inventory — every format is listed in the drawbridge://guide resource) and export it. Drawbridge decides where the lines go; you decide what connects to what. HOW TO GET A PRECISE RESULT: device output the user pasted IS the source — pass it unchanged, never rewritten as DOT. When you write DOT yourself: set kind= on EVERY device so it draws as the real thing rather than a neutral box (firewall, waf, ips, vpn-gateway, proxy, nac, router, switch, l3-switch, load-balancer, wifi-ap, wlc, … — full list in the drawbridge://guide resource). Put speed= on every cable ("10G", "1G"), and link= where the cable MEANS something (ipsec, trunk, lag, wan, mgmt, wireless, conduit, fieldbus, ha). Never set pos=, width= or height=: Drawbridge lays out and routes — placing devices yourself is what makes a diagram look generated. READ THE notes IN THE RESULT AND FIX YOUR SOURCE: they name each line that was skipped or adjusted, and an unrecognised kind silently becomes a plain box otherwise. Iterate until the notes are empty. 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": {
      "source": "<source>"
    },
    "name": "create_diagram"
  }
}

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.
sourceYesTopology text: Graphviz DOT, Mermaid, CSV, CDP/LLDP neighbour output from most switch vendors, a FortiLink topology dump, Containerlab, Meraki or UniFi JSON, or an Ansible inventory. Device output goes in exactly as the user pasted it — do not rewrite it as DOT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that results contain `notes` naming skipped or adjusted lines, that unrecognised `kind=` values silently degrade to a plain box, that the agent must iterate until notes are empty, that results carry a suggested `name`, and that the tool owns layout/routing so pos/width/height must never be set. This is precisely the behaviour an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is high-value but the block is long and carries no markup structure — the how-to, kind-selection and file-naming guidance run together as one wall of SHOUTED sentences, so key directives are harder to scan than they need to be. Front-loading of purpose is good, but the middle section could be tightened without losing information.

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?

No output schema exists, and the description compensates by explaining what comes back (`notes`, suggested `name`) and how to act on it. For a 4-parameter generator with a 9-value enum it covers input fidelity, output-format choice, error recovery, and file layout conventions — nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description does add meaning beyond the schema for `source` (pass pasted device output verbatim, never rewrite as DOT) and for `kind` (which format fits which downstream use), but `name`, `theme` and the mechanical enum values are already fully documented in 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+resource ('Generate a routed, laid-out network diagram from topology text ... and export it'), enumerates the accepted input formats, and frames the division of labour ('Drawbridge decides where the lines go; you decide what connects to what'). An agent can distinguish this from edit_diagram/describe/validate without inspecting schemas.

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?

Gives strong per-format selection advice for the `kind` parameter (drawio when the user will edit, svg to embed, png for inline chat, describe.json to read back, csv/netbox for cable schedules, clab.yml to deploy) and states the key rule that pasted device output is passed unchanged. It does not explicitly name sibling tools or state when to use edit_diagram/validate instead, so it stops short of full when/when-not guidance.

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