Skip to main content
Glama

Canvas Update Node

aimixer_canvas_update_node
Idempotent

Patch an existing NOTE/TEXT/idle generation node in place with CAS and idempotent request_id. Same node ID and edges; never delete/recreate.

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": {
      "project_id": "<project_id>",
      "expected_rev": "<expected_rev>",
      "request_id": "<request_id>",
      "node_id": "<node_id>",
      "patch": "<patch>"
    },
    "name": "aimixer_canvas_update_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
node_idYes
project_idYes
request_idYes
expected_revYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotentHint and destructiveHint=false, and the description still adds real substance: CAS via expected_rev, an idempotent request_id, and the guarantee that node ID and edges are preserved. It stops short of saying what happens on a revision conflict (error vs. retry) or how unpatched fields are treated.

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?

Two tight sentences, zero filler, with the operation and safety semantics front-loaded. Nothing could be removed without losing information.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and annotations plus the CAS/idempotency notes cover the mutation's safety profile. However, for a nested-object patch tool, the absence of any statement about which node fields are patchable or conflict/error behavior leaves a real gap for correct invocation.

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 0% and the schema is nested, so the description must carry the load. It meaningfully explains three of five params (node_id identity preservation, expected_rev as CAS token, request_id as idempotency key) but says nothing about the patch object's content/geometry/generation sub-schemas or project_id, leaving the most complex parameter undocumented.

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?

Specific verb+resource: 'Patch an existing ... node in place', and it narrows scope to NOTE/TEXT/idle generation nodes while ruling out delete/recreate. An agent knows exactly what class of node this mutates, though it never names a sibling (e.g., create vs. update) to sharpen the contrast further.

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

Usage Guidelines4/5

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

'existing ... in place' and 'never delete/recreate' tell the agent to reach for this only when the node already exists and should keep its identity. The 'idle generation node' qualifier implies a precondition (node must not be mid-generation), but no explicit alternative tool is named for the non-idle or create cases, keeping it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources