Skip to main content
Glama

ai_modeling_canvas_save

Save a complete Canvas graph while enforcing an expected revision, so concurrent edits raise conflicts instead of overwriting existing work.

Instructions

Save a complete Canvas graph against an expected revision; conflicts are never overwritten.

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": {
      "canvasId": "<canvasId>",
      "clientId": "<clientId>",
      "revision": "<revision>",
      "nodes": "<nodes>",
      "edges": "<edges>"
    },
    "name": "ai_modeling_canvas_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYes
nodesYes
canvasIdYes
clientIdYes
revisionYes
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

The description adds real value beyond the annotations by disclosing the optimistic-concurrency contract ('conflicts are never overwritten'), which is consistent with destructiveHint=false. However, it says nothing about what happens on the conflict path (error type, returned revision), whether a successful save bumps the revision, or what clientId is for, leaving the mutation's outcomes under-specified.

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?

A single tight sentence that front-loads the operation and its most consequential constraint. No filler, no restatement of the tool name.

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

Completeness2/5

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

This is a complex mutation with a deeply nested graph schema, six parameters at 0% coverage, and no output schema. The description covers only the conflict semantics; it omits the shape of a successful response (new revision, saved graph), idempotency behavior for clientId, and any validation expectations, which is thin for a tool of this complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so every one of the six parameters is documented by name alone. The phrase 'expected revision' usefully explains concurrency semantics for the revision parameter, and 'complete graph' implies nodes/edges replace rather than merge, but canvasId, projectId, and especially clientId (idempotency key? caller identity?) receive no meaning anywhere.

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?

Names a specific verb (save) and resource (Canvas graph) with the distinguishing modifier 'complete', which separates a full-graph write from the incremental editing implied by a sibling like ai_modeling_canvas_graph_edit. It stops short of naming any alternative, but the operation is unambiguous.

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?

The expected-revision clause implies the tool is for full replacements under optimistic concurrency, which hints at when it applies, but there is no explicit when-not guidance, no mention of which sibling to use for partial edits, and no explanation of where a valid revision comes from (presumably ai_modeling_canvas_get).

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