Skip to main content
Glama

Canvas Create

aimixer_canvas_create
Idempotent

Use when the user asks to create a new Canvas project, moodboard or storyboard (for example: new project with a photo, title and frame). Creates a native Canvas draft from semantic operations. For a storyboard, pipeline, branching, comparison or moodboard, use the shared layout_composition operation AFTER adding/configuring draft nodes and exact connections. It positions group frames in a near-square ceil(sqrt(N))-column grid, row-major, with no overlaps. Read capabilities first. Use the SAME request_id when retrying. Layout and creation never run media generation or charge coins. Use direct references unless the user needs a character/location sheet; do not invent paid stages. With parent_project_id the new project is a sub-canvas inside that project and its card (a frame with subcanvasId) is placed on the parent canvas; the result says card.placed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
operationsYes
request_idYes
parent_project_idNoCreate a sub-canvas inside this owned project and put its card on the parent canvas.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / parent_project_id
      Added value: +{
      +  "description": "Create a sub-canvas inside this owned project and put its card on the parent canvas.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description builds on that with the exact mechanics: same request_id on retry, no media generation or coin charges, deterministic near-square ceil(sqrt(N)) grid layout with no overlaps, and parent_project_id creating a sub-canvas whose card is placed on the parent, reported via card.placed. This is substantial cost, side-effect and result-shape disclosure beyond the structured fields.

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?

Front-loaded with the triggering condition, then dense operational detail; nearly every sentence carries a rule an agent would otherwise get wrong (retry id, cost-free layout, grid geometry). It runs long and packs several unrelated constraints (naming conventions, paid stages, parent cards) into one block, which slightly hurts scannability but not comprehension.

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?

For a creation tool with an output schema, the description correctly avoids explaining return values except where behavior matters (card.placed). The gap is the operations payload: with 25% schema coverage and untyped array items, an agent still cannot construct a valid operations list from this definition alone, and is only told to 'read capabilities first' as a workaround.

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 only 25%, with parent_project_id being the sole documented property, and the description does cover that one well (sub-canvas semantics, card placement on parent). It also gives retry semantics for request_id and says operations are 'semantic operations' that must be added/configured before layout composition. However, the shape of the operations array items (max 200, arbitrary objects) and the meaning of name are never explained, leaving the most-used parameter underspecified.

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 ('Creates a native Canvas draft from semantic operations') with concrete examples ('new project with a photo, title and frame'), so the agent knows exactly what the tool produces. It clarifies the storyboard/moodboard path via the shared layout_composition operation, but never mentions the available sibling aimixer_canvas_create_storyboard, leaving an overlap an agent could mis-route on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear triggering context ('Use when the user asks to create a new Canvas project'), a prerequisite ('Read capabilities first'), a retry protocol ('Use the SAME request_id when retrying'), and a restraint rule ('do not invent paid stages', 'Use direct references unless the user needs a character/location sheet'). It stops short of explicitly excluding the closest sibling tool, so the when-not is only partial.

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