Skip to main content
Glama

ai_modeling_canvas_continue

Continue a Canvas agent turn by submitting the user's chosen options and required inputs with an idempotent request ID, so retries return the original job instead of creating duplicates.

Instructions

continue a Canvas agent turn using the requested user choice. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_canvas_continue"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only give readOnly=false, openWorld=true, destructive=false; the description adds real behavior beyond that — Studio account scoping, idempotency via a stable request_id, reuse returning the original job, conflicting input on reuse, and a hard rule against blind retry after outcome_unknown. That is the kind of context an agent cannot get from the annotations. It does not mention cost/billing implications of running the remote agent, which is the remaining gap.

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?

Three short, front-loaded sentences with no filler, and the idempotency and retry rules are placed where they will be read before invocation. The telegraphic phrasing ('changed input conflicts') is dense but not ambiguous in context.

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?

There is no output schema and no rich annotations, so the description carries the burden, and it does cover the critical safety story (idempotency, conflict, unknown-outcome retry). It does not cover what a successful continuation returns, how multi-question answers must be supplied, or how the accept_variable_cost confirmation interacts with the call, which matters for a nested-object remote-agent tool.

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?

Top-level schema coverage is 0%, and the `parameters` object is a nested structure with nine properties including required accept_variable_cost and turn_id. The description adds meaning only for request_id (stable, don't reuse the original turn.requestId); it says nothing about how selected_option_ids, other_texts, attachment_ids, or confirmed_parts are meant to be assembled, leaving the agent to infer the answer-shape contract from inline schema text alone.

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: 'continue a Canvas agent turn using the requested user choice'. That is clearly distinguishable from create/run/get siblings. It does not name the closest alternative (ai_modeling_canvas_answer_plan) or explain the relationship, so it stops short of full sibling differentiation.

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?

Usage is only implied: you continue a turn when the agent has asked for a user choice. The retry constraint ('outcome_unknown must never be blindly retried') is a useful operational rule, but there is no explicit when-not guidance and no reference to which sibling to use if there is no pending turn.

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