Skip to main content
Glama

ai_modeling_canvas_review

Approve or revoke an image review checkpoint at a specified revision, then use the returned downstream node IDs to continue the canvas workflow.

Instructions

Approve or revoke an image review checkpoint at an expected revision. Returns downstream node IDs; run those separately to continue.

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>",
      "nodeId": "<nodeId>",
      "revision": "<revision>",
      "approved": "<approved>"
    },
    "name": "ai_modeling_canvas_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
approvedYes
canvasIdYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, open-world operation. The description adds meaningful behavior beyond that: it implies optimistic concurrency through the expected revision and explains that downstream node IDs are returned and must be run separately. It still omits what happens on a stale revision and the exact side effects of approval versus revocation.

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 sentences, front-loaded with the core action and followed by the essential continuation behavior. There is no filler or redundant restatement.

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?

The description covers the key return-and-continue behavior, which is important because there is no output schema. However, with four required parameters and zero schema descriptions, it remains incomplete on parameter meaning and failure behavior for revision mismatches.

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 the description must carry parameter meaning. It lightly implies the purpose of 'revision' and 'approved', but it never explains 'canvasId' or 'nodeId', leaving two required parameters completely opaque.

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 description states a specific verb pair ('Approve or revoke') and a specific resource ('image review checkpoint'), which is much clearer than a generic update tool. It does not, however, distinguish itself from sibling canvas tools or name an alternative workflow explicitly.

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?

It gives an important precondition ('at an expected revision') and a next-step instruction ('run those separately to continue'), but it does not say when not to use this tool or how to choose among the many sibling canvas tools.

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