Skip to main content
Glama
dgmo-mcp
by diagrammo

put_space_diagram

DestructiveIdempotent

Writes DGMO diagrams to a Diagrammo Cloud space by folder and title: updates an existing diagram or creates a private one, returning created/updated status.

Instructions

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 { action: "created" | "updated", id, title, folder, version }. Needs DGMO_API_KEY (a space API key) in the server environment. Errors name the cause: 401 bad or revoked key, 403 not allowed, 404 no such space or folder, 409 another write landed first (call again). Call validate_diagram first; this does not validate.

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>",
      "title": "<title>",
      "dgmo": "<dgmo>"
    },
    "name": "put_space_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
dgmoYesDGMO diagram markup
titleYesDiagram title within the folder.
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

A4.9/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/idempotent, but the description adds materially: created diagrams are private, the upsert semantics keyed by folder+title, the required DGMO_API_KEY environment variable, a concrete error taxonomy (401 revoked key, 403, 404 space/folder, 409 retry), and a documented return payload. The 409 'call again' guidance is exactly the kind of retry behavior an agent cannot get from annotations.

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?

Front-loaded with the action and its upsert rule, then return shape, auth, errors, and the validate prerequisite in descending order of importance. Dense but every sentence carries operational information; nothing is padding.

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?

With no output schema, the description compensates by spelling out the returned JSON fields (action, id, title, folder, version). Auth requirements, error causes, and the pre-validation step are all covered, so an agent has everything needed for a four-parameter write tool.

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 still adds meaning by explaining that folder and title jointly identify the target diagram (the upsert key) and that newly created diagrams default to private. The only gap is that it doesn't restate folder path syntax, which the schema already covers.

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 ('Write a DGMO diagram into a Diagrammo Cloud space') plus the exact keying scheme ('by folder and title') and the upsert outcome (update existing, create private if none). An agent can distinguish this write path from read siblings like get_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 an explicit prerequisite and exclusion: 'Call validate_diagram first; this does not validate,' naming the sibling and the condition that selects it. It also tells the agent that re-sending identical source is a no-op, which removes a common unnecessary-call concern.

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