Skip to main content
Glama

architecture_diagram

Read-onlyIdempotent

Build Mermaid diagrams from explicit nodes and edges, sanitizing labels and rejecting dangling edges to ensure valid architecture visuals.

Instructions

Build Mermaid from explicit nodes and edges. Sanitizes labels and rejects dangling edges.

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": {
      "nodes": "<nodes>",
      "edges": "<edges>"
    },
    "name": "architecture_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYes
nodesYes

Output Schema

NameRequiredDescriptionDefault
mermaidNo
limitationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • removedInput schema / properties / edges / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / nodes / items / additionalProperties
      Removed value: -false
  2. First observedv0.4.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the disclosure of validation behavior: labels are sanitized and dangling edges are rejected. That is genuinely useful for anticipating failure modes. It stops short of saying how rejection surfaces (error vs. silent drop), which would complete the picture.

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

Conciseness5/5

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

Two short sentences, zero filler, with the generation purpose front-loaded and the validation caveat second. Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and annotations cover safety. But with zero schema parameter descriptions, the definition leaves an agent guessing about id format, size limits, and dangling-edge error semantics. Adequate but with clear gaps for a two-parameter generator.

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 0%, so the description must carry the burden, and it only names the two inputs implicitly ('nodes and edges'). It conveys the relationship constraint (edges must connect to declared nodes) but does not explain the node id pattern, the 40-node/80-edge caps, or what a sanitized label means. Partial compensation only.

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 states a specific verb and resource: 'Build Mermaid from explicit nodes and edges.' An agent immediately knows this generates a Mermaid diagram from a supplied graph. It does not, however, distinguish itself from diagram-adjacent siblings such as sequence_diagram or c4_model.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives like sequence_diagram or c4_model, which an agent could easily confuse with this tool. The only implied usage signal is that the caller must already have explicit nodes and edges.

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