Skip to main content
Glama
dgmo-mcp
by diagrammo

get_space_diagram

Read-onlyIdempotent

Retrieves a diagram from a Diagrammo Cloud space by ID or title, returning its folder, chart type, version, update time, and source as JSON.

Instructions

Read a diagram from a Diagrammo Cloud space, by id or by title in folder. Titles match case-insensitively. Returns JSON { id, title, folder, chartType, version, updatedAt, source }. Needs DGMO_API_KEY (a space API key) in the server environment. Errors when the key is refused (401/403) or nothing matches (404); list_space_diagrams shows what is there.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "space_id": "<space_id>"
    },
    "name": "get_space_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoDiagram id. Takes precedence over title.
titleNoDiagram title, when no id is given.
folderNoFolder path from the space root, e.g. "docs/architecture". Omit for the root.
space_idYesThe space the API key belongs to (the key does not name it). Shown beside the key when it is made at https://online.diagrammo.app/account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.16
    • changedInput schema / properties / space_id / description
      Previous value: -"The space the API key belongs to (the key does not name it)."New value: +"The space the API key belongs to (the key does not name it). Shown beside the key when it is made at https://online.diagrammo.app/account."
  2. Addedv0.29.11

TDQS

A5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), but the description adds genuinely new behavioral facts: it returns a concrete JSON object with named fields, requires DGMO_API_KEY in the server environment, and fails with 401/403 for a refused key versus 404 for no match. Those auth and failure-mode disclosures are exactly the context an agent needs to handle the call.

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?

Three compact sentences ordered by importance: what it does and how to address it, what it returns, then auth and error behavior with an escape hatch. No filler, and the most decision-relevant information (id vs title, precedence) is front-loaded.

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

Completeness5/5

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

There is no output schema, yet the description supplies the return shape inline, along with the environment prerequisite and the two failure classes. For a single-lookup read tool with four documented parameters, nothing an agent needs to invoke it correctly or recover from an error is missing.

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

Parameters5/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, but the description adds matching semantics the schema does not state: titles match case-insensitively, and id wins over title when both are supplied. Folder scoping is named in the body rather than left only to the property 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?

States a specific verb and resource ('Read a diagram from a Diagrammo Cloud space') plus the two lookup keys, and the title makes clear it is a single-item fetch rather than the sibling list_space_diagrams enumerator. An agent can distinguish it from put_space_diagram and list_space_diagrams without opening any schema.

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

Usage Guidelines5/5

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

Gives the selection rule between the two addressing modes ('by `id` or by `title` in `folder`') and resolves ambiguity by declaring id precedence. It also names the discovery alternative explicitly ('list_space_diagrams shows what is there'), so an agent that does not know a diagram id is routed correctly before hitting a 404.

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