it-architecture
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ITARCH_OUTPUT_DIR | No | Directory where output SVG files are saved | ~/architecture-diagrams |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_authoring_guideA | Read this first. Returns the complete notation for describing an IT architecture (compact DSL + equivalent JSON), the available styles, group kinds and a worked example. No arguments. |
| list_stylesA | List the available drawing styles (cloud, azure, material, c4, blueprint, whiteboard, minimal, neon, slate) with a description of each look. |
| list_node_typesA | List every component icon (server, database, queue, k8s, firewall, ...) with its category and the aliases that map onto it. |
| validate_architectureA | Parse a diagram without drawing it. Reports every syntax/reference error at once, plus warnings about orphan nodes, empty groups and unknown icon types. Cheap to call before rendering. |
| render_architectureB | Draw an IT architecture and save it as a standalone .svg file (optionally in several styles at once). Layout, routing and grouping are automatic - never supply coordinates. Returns the absolute file paths. |
| render_all_stylesA | Render the same architecture once per available style into one directory, so a human can pick the look they want. Files are suffixed with the style name. |
| preview_architectureA | Return the SVG markup inline instead of writing a file. Use when the client can display or post-process SVG directly. |
| convert_notationA | Convert a diagram between the compact DSL and the JSON spec (both directions), normalising it on the way. Useful for editing a diagram that was written in the other notation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: guide, listing of styles, listing of node types, validation, rendering, multi-style rendering, preview, and notation conversion. No overlaps.
All tools follow a consistent verb_noun pattern in snake_case, e.g., list_styles, render_architecture, convert_notation.
Eight tools cover the core workflow of IT architecture diagramming without being excessive or insufficient.
The tools provide complete lifecycle support: learning (guide), configuration (styles, node types), validation, rendering, preview, and notation conversion. No obvious gaps.