dgmo-mcp
OfficialServer 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_diagramA | Render DGMO markup to SVG or PNG. Returns SVG text or base64 PNG image. When format is "png", also saves the image to a temp file and returns the path. For DGMO syntax call get_language_reference (e.g. color a label with a trailing color name: "Sales red"). |
| share_diagramA | Generate a shareable diagrammo.app URL for a DGMO diagram. |
| open_in_appA | Open a DGMO diagram in the Diagrammo desktop app (macOS only). Falls back to browser preview if the app is not installed. Pass |
| check_app_installedA | Check whether the Diagrammo desktop app is installed (macOS). Call this ONCE before choosing how to show a diagram. If installed, the preferred output is to save the .dgmo source and open that file live in the app (open_in_app with filePath) — do NOT default to an online share URL. If not installed, fall back to the online share URL. |
| list_chart_typesA | List all supported DGMO chart types with descriptions. |
| get_language_referenceC | Get the DGMO language reference documentation. Optionally filter by chart type. |
| preview_diagramA | Render one or more DGMO diagrams and open an HTML preview in the browser. Supports theme toggle and optional source display. For DGMO syntax call get_language_reference (e.g. color a label with a trailing color name: "Sales red"). |
| generate_reportA | Generate a polished HTML report with multiple DGMO diagrams, table of contents, and optional source blocks. Opens in browser by default. For DGMO syntax call get_language_reference (e.g. color a label with a trailing color name: "Sales red"). |
| validate_diagramA | Validate DGMO markup without rendering. Returns structured parse errors and warnings. Much faster than render_diagram — use this to check syntax before rendering. |
| suggest_chart_typeA | Suggest the best DGMO chart type for a user's plain-English diagram request. ALWAYS CALL THIS FIRST when creating a new diagram — it prevents guessing and is the authoritative selection mechanism. Returns one of two shapes: (1) a confident pick (high/medium) with the top match's syntax, or (2) an '⚠️ ASK THE USER' directive when the choice is ambiguous or nothing matched. On an ASK-THE-USER directive, do NOT pick a type yourself — present the listed candidates to the user and wait for their choice before generating. |
| get_examplesA | Get example DGMO diagrams for a chart type. Returns real-world examples from the gallery that demonstrate syntax patterns. Use these as few-shot references when generating new diagrams. |
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 11 tools
Each tool targets a distinct phase of the diagram workflow: validation, rendering, previewing, sharing, app integration, reference lookup, and chart suggestion. There is some adjacency between render_diagram, preview_diagram, and generate_report, but their output formats and purposes are clearly separated.
All tool names follow a consistent verb_noun pattern using lowercase snake_case: render_diagram, share_diagram, list_chart_types, suggest_chart_type, validate_diagram. There are no style deviations or vague verbs.
Eleven tools cover the full DGMO workflow from language reference and chart suggestion through validation, rendering, preview, report generation, and sharing. The count feels intentional and well-scoped for the domain.
The tool surface covers the complete diagram lifecycle: learn syntax, pick a chart type, get examples, validate, render to multiple formats, preview, generate reports, share, and open in the desktop app. No obvious dead ends; each workflow path has supporting tools.