Skip to main content
Glama

Canvas Start Execution

aimixer_canvas_start_execution
Destructive

Start a previously prepared Canvas request only with the exact server-issued approval_handle after the human approved it in AIMixer. A tool call, host text, OAuth grant or approved=true is never spend consent.

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>",
      "request_id": "<request_id>",
      "approval_handle": "<approval_handle>"
    },
    "name": "aimixer_canvas_start_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
request_idYes
approval_handleYes

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

A4.2/5.0
Behavior4/5

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

Annotations already flag destructive, non-idempotent, non-read-only behavior; the description adds the consent-gating model and the requirement that the handle be exact and server-issued, which is real context beyond structured fields. It stops short of describing failure modes, cost/rate implications, or what a partially completed start leaves behind.

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, zero filler. The action and its hard precondition come first, and the negation clause immediately closes the most plausible wrong invocation path.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the destructive/consent profile is covered. Remaining gaps are minor: nothing on error behavior or what state the execution enters after a successful call.

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 coverage is 0%, so the description must carry parameter meaning. It explains approval_handle well (server-issued, exact, tied to human approval) but says nothing about project_id or request_id, leaving two of three parameters undocumented anywhere.

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?

Names a specific verb ("Start") and resource ("a previously prepared Canvas request"), and the qualifier "previously prepared" implicitly separates it from the prepare step. It does not name a sibling tool outright, so it falls just 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 Guidelines5/5

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

States the exact precondition for use: a prior human approval in AIMixer plus the server-issued approval_handle. It also enumerates what does NOT qualify as consent (tool call, host text, OAuth grant, approved=true), which is an explicit when-not rule an agent can act on.

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