endiagram
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EN_API_URL | No | API endpoint for the EN Diagram service | https://api.endiagram.com |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_systemC | Structural signal. You describe the system, the tool computes structural facts. All computation is deterministic — no AI inside. EN syntax: subject do: action needs: inputs yields: outputs. |
| renderB | Render an EN dependency graph as a publication-quality SVG image. |
| detailC | Deep structural analysis — concurrency, flow landmarks, resilience, dominator tree, min-cuts. |
| distanceC | Shortest path between two nodes with subsystem crossing annotations. |
| diffC | Structural diff between two systems — topology, role, and subsystem changes. |
| traceC | Follow directed flow from node A to node B with role and subsystem annotations. |
| extractB | Extract a named subsystem as standalone EN source code. |
| impactC | Blast radius — remove a node and see what disconnects. |
| evolveC | Dry-run architectural changes — apply a patch and see the structural delta. |
| betweenB | Betweenness centrality for a node — what fraction of all shortest paths flow through it. |
| categorizeC | Auto-discover subsystem boundaries from dependency structure. |
| composeC | Merge two EN graphs into one with entity linking. |
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 12 tools
Most tools target distinct graph operations, but trace, distance, and between all revolve around paths and centrality, while analyze_system, detail, and categorize overlap in structural analysis. Descriptions help but an agent could reasonably pick the wrong tool for some analytical tasks.
Tool names are mostly single lowercase words, but they mix verbs, nouns, and prepositions (between, distance, impact, detail), and analyze_system breaks the pattern with snake_case. There is no consistent verb_noun or predictable naming convention.
Twelve tools is well-scoped for a dependency-graph analysis server. Each tool has a recognizable responsibility within analysis, rendering, transformation, and composition, without feeling padded or thin.
The toolkit covers traversal, centrality, structural diffing, subsystem discovery, deep analysis, rendering, merging, and dry-run evolution. Minor gaps like explicit node creation/deletion or cycle detection exist, but the server's analytical focus is well covered.