diagram-forge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | No | Your Google Gemini API key | |
| OPENAI_API_KEY | No | Your OpenAI API key |
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 |
|---|---|
| generate_diagramA | Generate an architecture diagram from a text prompt. Args:
prompt: Description of what to generate
diagram_type: Type of diagram (architecture|data_flow|component|sequence|integration|infographic|c4_container|exec_infographic|generic)
theme: Background theme (light|dark). Default: light — the portfolio-wide
default (rep / marketing / CISO-facing output is the common case). Pass
theme="dark" for a dark charcoal canvas. This single switch governs the
background; you do NOT need to describe a background color in |
| edit_diagramA | Edit an existing diagram based on instructions. Args: image_path: Path to the existing diagram image prompt: Edit instructions provider: Image generation provider (gemini|openai) resolution: Output resolution (auto-detect if not specified) reference_images: Additional reference image paths output_path: Where to save the result |
| list_templatesA | List all available diagram templates with descriptions. |
| list_providersA | List configured providers with status, models, and health information. |
| list_stylesA | List all available style reference images. |
| get_usage_reportA | Get usage and cost report for diagram generations. Args: days: Number of days to report on (default: 30) group_by: Group results by 'provider', 'diagram_type', or 'day' |
| configure_providerA | Configure an API key for a provider (sets environment variable for current session). Args: provider: Provider name (gemini|openai) api_key: The API key to set |
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 7 tools
Each tool has a clearly distinct purpose: generation, editing, listing resources, usage reporting, and provider configuration. No two tools overlap in a way that would cause misselection.
All tool names follow a consistent verb_noun pattern in snake_case (generate_diagram, edit_diagram, list_templates, configure_provider, etc.). The use of 'list' for multiple resource types and 'get' for a report is a reasonable variation within the same structural convention.
Seven tools is well-scoped for a diagram generation service, covering creation, editing, resource discovery, configuration, and reporting without unnecessary bloat.
The core lifecycle of diagram generation and editing is covered, along with resource discovery and provider management. The main gap is the lack of tools for managing previously generated diagrams (e.g., listing or deleting outputs), but this is a minor oversight since outputs are saved as files.