Skip to main content
Glama

ai_modeling_canvas_graph_edit

Edit a saved Canvas graph locally by adding, grouping, duplicating, laying out, expanding image batches, replacing uploads, and undoing/redoing changes; save the result to a separate file.

Instructions

edit a saved Canvas graph locally: copy, group, layout, expand image batches, replace uploads and persistent undo/redo; save separately

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": {
      "graph_path": "<graph_path>",
      "destination_path": "<destination_path>",
      "actions": "<actions>"
    },
    "name": "ai_modeling_canvas_graph_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsYes
graph_pathYes
destination_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, so the safety profile is largely covered; the description adds two useful facts beyond that: undo/redo is persistent across calls, and results are saved separately rather than in place. It says nothing about whether actions are applied atomically or in order, what happens on partial failure, or how large action batches are bounded (schema caps at 200), which is the kind of context this tool would benefit from.

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

Conciseness4/5

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

A single front-loaded sentence with the verb and object first, then a compact operation list. The clause structure is telegraphic and slightly awkward ('expand image batches', 'replace uploads and persistent undo/redo'), but no sentence is wasted.

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?

For a tool with a very large action union, no output schema, and zero schema parameter documentation, the description is far too thin: it does not explain undo/redo scope (per-call vs per-graph), whether the destination may equal the source, ordering of actions, or what the caller gets back. Key call-time facts an agent needs are missing.

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% and the description names none of the three required parameters (graph_path, destination_path, actions) or explains their relationship. 'save separately' only weakly hints that destination_path is the output; nothing clarifies path format, overwrite behavior, or that actions is an ordered per-action union with its own semantics (keep_children, offset, expected_asset_ids, catalog fallback).

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?

States a specific verb and resource ('edit a saved Canvas graph locally') and enumerates the operation families (copy, group, layout, expand images, replace uploads, undo/redo), which is enough to distinguish it from read/create/delete siblings. It is not fully differentiated from the similarly named 'local_edit' / 'project_edit' / 'segmentation_edit' siblings, but the scope statement itself is clear.

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?

'locally' and 'save separately' imply that the source file is not modified in place and that the caller must supply a destination, which is implicit when-to-use guidance. There is no explicit statement of when to prefer this over the sibling edit tools or over canvas_append_template/canvas_copy_shared, and no exclusions or prerequisites are given.

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