Blueprint
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_c4_diagram_toolA | Create a C4 architecture diagram from structured data. Generates diagram source code (Mermaid or PlantUML) from explicitly defined elements, relationships, and boundaries. Args: diagram_type: C4 diagram type: context, container, component, deployment, or dynamic title: Diagram title elements: List of C4 elements, each with: type, alias, label, description, technology relationships: List of relationships, each with: source, target, label, technology, direction boundaries: List of grouping boundaries, each with: type, alias, label, element_aliases output_format: Output format: mermaid (default) or plantuml Returns: Diagram source code in the requested format. |
| scan_codebase_toolA | Scan a project directory and return a structural overview. Returns information about the project including: detected language, framework, directory tree, dependencies, entry points, and config files. Does NOT interpret code — use this as a starting point for analysis, then read specific files to understand the architecture. Args: project_path: Absolute or relative path to the project root directory max_depth: Maximum directory depth to scan (default: 3) Returns: JSON object with project structure information. |
| get_c4_reference_toolA | Get C4 model reference documentation. Returns documentation about C4 element types, diagram types, and relationship conventions. Use this to understand what elements are available and how to structure create_c4_diagram inputs. Args: topic: Reference topic: elements, diagrams, relationships, or all Returns: Markdown documentation for the requested topic. |
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 3 tools
Each tool has a clearly distinct purpose: one creates diagrams from structured data, one provides reference documentation, and one scans codebases. No overlap in functionality.
All tools follow a consistent verb_noun_tool pattern (create_c4_diagram_tool, get_c4_reference_tool, scan_codebase_tool) with snake_case, making them predictable.
Three tools is reasonable for the server's focus on C4 diagrams and codebase scanning, though it feels slightly minimal. Each tool serves a distinct function without bloat.
The server covers diagram creation and reference but lacks automatic conversion from code to C4 elements or tools to manage saved diagrams. The codebase scanner provides structure but not interpretation, leaving a gap.