Skip to main content
Glama

Drawbridge Network Diagrams

validate

CHECK TOPOLOGY TEXT BEFORE DRAWING IT: reads the same source create_diagram would and reports what it found — the format it detected, how many devices and links it would draw, and every line it would skip or adjust, with the line number and the reason. An unknown kind= names the nearest real one. Nothing is laid out, routed or rendered, so it is far cheaper than a draw: call it, fix what it names, then call create_diagram once. 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": "validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses that nothing is laid out, routed or rendered (i.e. no side effects), that unknown `kind=` values are resolved to the nearest real one rather than rejected, that skipped lines are itemized with line number and reason, and that results carry a suggested `name`. It stops short of stating outright that the input is never modified and says nothing about failure behavior when the text cannot be parsed at all.

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 operative instruction and its rationale are front-loaded before any detail, and the middle section on what the report contains is dense and useful. The closing two sentences about per-diagram directory layout are scope creep relative to validating text, though they do explain the returned `name` value and are the only place that convention is documented.

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?

With no output schema, the description must describe returns and does so concretely: detected format, device and link counts, per-line skips with reasons, and a suggested basename. What remains unstated is edge behavior — whether an unparseable input raises an error or returns an empty report, and whether warnings are surfaced in the same payload.

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?

The single `source` parameter already has 100% schema coverage enumerating every accepted format, so the schema does the heavy lifting and baseline 3 applies. The description adds only the framing that this is the same source `create_diagram` would consume; the stray "unknown `kind=`" reference is not one of this tool's parameters and could momentarily confuse an agent about where that argument lives.

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?

"CHECK TOPOLOGY TEXT BEFORE DRAWING IT" gives a specific verb and resource, then immediately states it reads the same source as `create_diagram` and reports format, device/link counts, and skipped lines. An agent can distinguish this dry-run validator from the drawing sibling without opening either schema.

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

Usage Guidelines5/5

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

The description gives an explicit operating sequence: "call it, fix what it names, then call `create_diagram` once," and names the alternative it is meant to precede. It also gives the reason to prefer it ("far cheaper than a draw"), which is the deciding condition.

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