Skip to main content
Glama

ai_modeling_canvas_extraction_plan

Read-only

Prepares SemanticSplit detection, auto/manual part extraction, and prompt edits from saved Canvas state; returns graph-edit actions and run parameters without saving or starting a paid run.

Instructions

Prepare SemanticSplit detection, auto/manual parts and per-result prompt edits from the saved webpage state. Returns graph-edit actions and separate run parameters; does not save or start a paid run.

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>"
    },
    "name": "ai_modeling_canvas_extraction_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsNo
actionNoinspect
amountNo
nodeIdYes
promptNo
canvasIdYes
revisionNo
splitModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds real value beyond that by clarifying that two kinds of output are returned (graph-edit actions and separate run parameters) and that no paid run is launched. This cost/side-effect boundary is exactly the kind of context annotations cannot express.

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?

Two tight sentences, front-loaded with the operation and ending with the negative side-effect constraint. Little waste, though the density of undefined internal terminology slightly reduces readability.

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 tool (8 params, 2 enums, no output schema, no param documentation) and the description does not explain the action modes or the shape of the returned graph-edit actions versus run parameters. For a tool this intricate, two sentences of prose are not sufficient to call it correctly.

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?

With eight parameters at 0% schema description coverage, the description must carry the load, but it only gestures at 'auto/manual parts' and prompt edits. The five-value action enum (inspect/detect/generate/regenerate/retry), amount, and revision have no meaning supplied anywhere, so the agent is left guessing about the central control parameter.

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 object: it 'prepares' detection, parts and prompt edits from saved webpage state, and explicitly contrasts with saving/starting a paid run. An agent can tell it is a dry-run planning tool, though the jargon 'SemanticSplit' and 'per-result prompt edits' is not defined.

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 'does not save or start a paid run' clause implicitly tells the agent to follow up with a graph-edit and a run tool, which is useful routing. However, no sibling tool is named and there is no explicit statement of when to prefer this over inspect/detect actions inside the same tool.

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