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. |
| share_diagramA | Generate a shareable diagrammo.app URL for a DGMO diagram. The source is compressed into the URL fragment, so nothing is uploaded and the link works for anyone who opens it; returns the URL as text. Errors when the compressed source exceeds the URL size limit (the error reports both sizes) — split or simplify the diagram, or use open_in_app / render_diagram instead. The source is not validated here; call validate_diagram first. |
| 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. Returns a sentence naming the output route the product prefers, plus JSON |
| list_chart_typesB | List all supported DGMO chart types with descriptions, grouped by family and, in data and business, by purpose. |
| get_language_referenceA | Get the DGMO language reference. With |
| 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. |
| 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. |
| 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. Call this first when creating a new diagram: it ranks the chart types against the request and, on a confident pick, appends that type's language-reference section, so no separate get_language_reference call is needed. It is not needed when editing an existing diagram, whose first line already declares its type. Returns one of two shapes: (1) a confident pick (high/medium) with the top match's syntax, or (2) an '⚠️ ASK THE USER' result when the choice is ambiguous or nothing matched. On an ASK-THE-USER result, present the listed candidates to the user and wait for their choice before generating, because the request alone does not settle which type they want. |
| 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. |
| put_space_diagramA | Write a DGMO diagram into a Diagrammo Cloud space, by folder and title: updates the diagram with that title in that folder, or creates it (private) when there is none. Re-sending identical source changes nothing. Returns JSON |
| get_space_diagramA | Read a diagram from a Diagrammo Cloud space, by |
| list_space_diagramsA | List every diagram in a Diagrammo Cloud space. Returns JSON |
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 14 tools
Most tools target clearly distinct purposes: language lookup (get_language_reference, list_chart_types, get_examples), authoring aids (suggest_chart_type, validate_diagram), output routes (render_diagram, preview_diagram, open_in_app, share_diagram), and cloud storage (put/get/list_space_diagram). The four output-route tools overlap conceptually, but the descriptions clearly delineate SVG/PNG text, browser HTML preview, desktop app, and shareable URL, and check_app_installed explicitly disambiguates open_in_app vs share_diagram. The reference-lookup tools are also carefully cross-referenced (suggest_chart_type appends the reference section, so get_language_reference is only needed on switch), leaving only minor residual ambiguity between render_diagram and preview_diagram.
All names are snake_case, verb-first, and follow a verb_noun pattern (render_diagram, validate_diagram, share_diagram, list_space_diagrams, get_examples). Minor deviations appear in put_space_diagram and open_in_app, which use a prepositional qualifier rather than a plain noun, but both remain predictable within their sub-groups (cloud CRUD uses put/get/list).
Fourteen tools is well within a healthy range and each one earns its place: authoring helpers, output routes, cloud CRUD, and reporting cover the domain without redundancy. The grouping into language/reference, render/output, and cloud storage is coherent and not padded.
The surface covers the full lifecycle of authoring (suggest, reference, examples, validate, render), delivery (preview, share, open, report), and cloud storage with put/get/list. The main gap is that the cloud space is read-write-list only — there is no delete or move/rename operation for space diagrams, and no folder-listing tool, which an agent managing a space would likely need.