arc-diagram
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_arc_diagram_dialectsA | List the supported arc-diagram visual dialects, their semantics and authoring constraints. |
| get_arc_diagram_contractA | Return the complete DiagramDef JSON contract plus the core authoring rules used by the renderer. |
| validate_arc_diagram_setA | Validate diagram identities, references, dialect constraints, steps and control legends without writing files. |
| create_arc_diagram_projectA | Create a complete interactive React Flow arc-diagram project from validated DiagramDef objects. The project includes edit mode, embed mode, light/dark themes, geometric probes, PNG export and a self-contained offline HTML build. |
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 4 tools
Each tool targets a distinct stage of the arc-diagram workflow: listing dialects, retrieving the contract, validating a set, and creating a project. There is no overlap or plausible confusion between the tools.
All tool names follow a consistent verb_noun pattern with the arc_diagram prefix: list, get, validate, and create. The naming is uniform and predictable.
Four tools is well-scoped for the server's purpose: discovery, contract access, validation, and project generation. Each tool earns its place and there is no redundancy.
The tool set covers the full stated pipeline from understanding dialects and the contract, to validating DiagramDef sets, to generating a complete project. There are no obvious gaps or dead ends within the declared domain.