Skip to main content
Glama

Canvas Prepare Execution

aimixer_canvas_prepare_execution

Validate selected configured Canvas generation nodes and return their current price/input summary. This does not submit generation. Reuse request_id to recover the same prepared request.

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>",
      "expected_rev": "<expected_rev>",
      "node_ids": "<node_ids>"
    },
    "name": "aimixer_canvas_prepare_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idsYes
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

B3.4/5.0
Behavior3/5

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

The description usefully explains why readOnlyHint=false despite being a 'validate' step: a prepared request is persisted and can be recovered by reusing request_id. That is real context beyond the annotations. It still omits how long a prepared request stays valid, what happens on an expected_rev mismatch, and whether the price summary is a quote or a commitment.

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?

Three short sentences, each doing distinct work: capability, the key negative boundary, and the replay semantic. The critical constraint is front-loaded in sentence two with nothing redundant.

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?

The output schema covers return values, so omitting them is correct, and the description supplies the essential non-obvious facts (non-submitting, persisted request, replayable request_id) for a four-required-parameter tool with zero schema descriptions. The residual gap is concurrency/lifetime behavior around expected_rev and prepared requests.

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, and it only partially does: request_id gets a clear replay semantic and node_ids is loosely tied to 'configured Canvas generation nodes'. project_id and especially the required expected_rev (an obvious optimistic-concurrency token) receive no explanation at all.

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: validate selected configured Canvas generation nodes and return a price/input summary. The clause 'This does not submit generation' implicitly separates it from aimixer_canvas_start_execution, though no sibling is named outright.

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 a negative boundary (not a submission) and a replay hint via request_id, which implies the intended pre-flight workflow. It never states when to choose this over aimixer_canvas_validate_workflow or aimixer_canvas_preview, nor what prerequisites (such as a matching expected_rev) must hold before calling.

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