Skip to main content
Glama

Drawbridge Network Diagrams

describe

Read a Drawbridge/draw.io network diagram and return its contents as structured JSON: devices, links, pages, layers and groups — for auditing or querying an existing drawing. 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": "describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesThe .drawio document as XML text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the read-only nature ('Read'), the return shape, and the presence of a `name` field, but says nothing about malformed XML handling, size limits, or side effects. Half the text is a downstream file-layout convention rather than tool behavior.

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?

The opening sentence is well front-loaded and informative. However, the second half is a prescriptive directory-naming workflow (<name>/<name>.drawio, .svg, .cables.csv) that does not help an agent select or invoke this read tool and dilutes the core purpose.

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

Completeness3/5

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

With no output schema, the description usefully compensates by naming the returned entities and the `name` field. But it omits error behavior and does not clarify why an agent would choose this over export for reading an existing diagram, leaving a real gap for a one-parameter tool whose output is the whole point.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description adds no syntax, encoding, or format guidance for `document` beyond what the schema already states ('The .drawio document as XML text').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Read a Drawbridge/draw.io network diagram and return its contents as structured JSON,' and enumerates the returned entities (devices, links, pages, layers, groups). This implicitly separates it from the create_diagram/edit_diagram siblings by scoping it to 'an existing drawing,' though it never names an alternative explicitly.

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?

Usage is only implied via the phrase 'for auditing or querying an existing drawing.' There is no explicit when-to-use vs when-not guidance and no routing to or away from export/validate, which are the closest siblings for reading an existing diagram. An agent must infer the boundary itself.

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