Skip to main content
Glama
dgmo-mcp
by diagrammo

list_space_diagrams

Read-onlyIdempotent

Lists every diagram in a Diagrammo Cloud space as JSON sorted by folder and title, helping you inspect diagram IDs, chart types, versions, and update times.

Instructions

List every diagram in a Diagrammo Cloud space. Returns JSON { diagrams: [{ id, title, folder, chartType, version, updatedAt }] }, sorted by folder then title. Needs DGMO_API_KEY (a space API key) in the server environment.

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": "list_space_diagrams"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses two genuinely useful traits: the exact returned JSON shape and the ordering ('sorted by folder then title'). It also states the authentication prerequisite (DGMO_API_KEY in the server environment), which annotations cannot convey.

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 short sentences, front-loaded with the action and scope, then the return contract, then the auth requirement. No filler or redundant restatement of the name.

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?

Although there is no output schema, the description supplies the response shape and sort order, and it covers the auth prerequisite for a single-parameter read tool. Minor gap: nothing about behavior for an empty space or a very large space.

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

Parameters3/5

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

Schema description coverage is 100% and the single space_id parameter is already explained in the schema, including the note that the key does not name its space. The description adds only the environment-level key requirement, not new semantics for the parameter itself, so the baseline 3 applies.

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

Purpose4/5

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

The first sentence gives a specific verb and resource ('List every diagram in a Diagrammo Cloud space'), which is unambiguous on its own. It does not name the single-item sibling get_space_diagram or explain the relationship, so the agent must infer the list-vs-get distinction from names alone.

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

Usage Guidelines3/5

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

Usage is only implied: 'list every diagram in a space' suggests enumeration rather than fetching one diagram or a chart type. There is no explicit when-to-use/when-not statement and no named alternative such as get_space_diagram or the authoring tools like put_space_diagram.

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