Skip to main content
Glama
diagrammo

dgmo-mcp

Official
by diagrammo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

open_in_app

Open a DGMO diagram in the Diagrammo desktop app (macOS only). Falls back to browser preview if the app is not installed.

Instructions

Open a DGMO diagram in the Diagrammo desktop app (macOS only). Falls back to browser preview if the app is not installed. Pass filePath to open a saved .dgmo file directly — the app opens THAT file, so in-app edits autosave back to it (one editable source of truth, live re-render). This is the preferred path when the app is installed: write the .dgmo source first, then open it here. Omit filePath for an ephemeral diagram (sends a deep link; the app creates its own copy).

Input Schema

NameRequiredDescriptionDefault
dgmoYesDGMO diagram markup
filePathNoAbsolute path to an already-saved .dgmo file. When set, the app opens this exact file for live editing instead of receiving a deep-linked copy. Any other value — relative, not .dgmo, or missing — is refused with an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.11
    • changedInput schema / properties / filePath / description
      Previous value: -"Absolute path to an already-saved .dgmo file. When set, the app opens this exact file for live editing instead of receiving a deep-linked copy."New value: +"Absolute path to an already-saved .dgmo file. When set, the app opens this exact file for live editing instead of receiving a deep-linked copy. Any other value — relative, not .dgmo, or missing — is refused with an error."
  2. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / filePath
      Added value: +{
+  "description": "Absolute path to an already-saved .dgmo file. When set, the app opens this exact file for live editing instead of receiving a deep-linked copy.",
+  "type": "string"
+}
  3. Addedv0.2.2
  4. Removedv0.1.21
  5. First observedv0.1.13

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses behavior beyond the annotations: macOS-only operation, browser-preview fallback, autosaving in-app edits back to the exact `filePath`, and deep-link copy creation when `filePath` is omitted. These details are consistent with `readOnlyHint=false`, `destructiveHint=false`, and `openWorldHint=true`.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and platform, then explains the saved-file path and ephemeral alternative. It is dense but every sentence carries useful operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the main behavior, platform constraint, fallback, and both parameter paths thoroughly. Since there is no output schema, it could have said more about the tool's return value or failure behavior when the app is unavailable, but the core invocation guidance is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics for `filePath`: it opens that exact saved file, enables autosave back to it, and is the preferred path, while omission creates an ephemeral copy. The `dgmo` parameter is not elaborated beyond the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: opening a DGMO diagram in the Diagrammo desktop app. It also distinguishes the app path from browser preview and from ephemeral deep-link opening, so an agent can tell what this tool is for without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage conditions: pass `filePath` to open a saved .dgmo source as the preferred path when the app is installed, and omit `filePath` for an ephemeral diagram. It also mentions fallback to browser preview, but it does not explicitly name sibling alternatives such as `check_app_installed` or `preview_diagram`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools