Skip to main content
Glama

Canvas Attach Scene Continuation

aimixer_canvas_attach_scene_continuation
Idempotent

Explicit WRITE of an owned finished scene's last frame and CAS graph connection to the following idle scene's verified first_frame slot. No payment or provider submit; unavailable modes/conflicting inputs fail closed; same request_id replays the exact edit.

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>",
      "source_scene_id": "<source_scene_id>",
      "target_scene_id": "<target_scene_id>",
      "expected_rev": "<expected_rev>",
      "request_id": "<request_id>"
    },
    "name": "aimixer_canvas_attach_scene_continuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
request_idYes
expected_revYes
source_scene_idYes
target_scene_idYes
source_result_indexNo

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
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the baseline is partly covered. The description adds real value on top: it states fail-closed behavior for unavailable modes and conflicting inputs, the exact-replay semantics of a repeated request_id, and that no payment or provider submit occurs. It does not explain what happens to an existing continuation link when re-attaching, which is the one behavioral gap left.

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 clauses, front-loaded with the write action, followed by scope limits and retry semantics; no filler sentences. The density of internal jargon ("CAS graph connection", "verified first_frame slot") costs a little readability but every clause carries information.

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?

An output schema exists, so return values need no prose, and the description covers safety, idempotency, and fail-closed behavior. For a six-parameter mutation with an expected_rev concurrency guard and zero schema descriptions, though, it omits what a revision mismatch actually produces and how source_result_index selects a frame, which an agent needs before calling.

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 six parameters rest entirely on the description, which only glosses request_id (replay) and hints at revision conflict through "conflicting inputs fail closed". The roles of source_scene_id, target_scene_id, project_id, expected_rev and especially source_result_index (which result on a multi-result source scene) are never explained, leaving the agent to guess required values.

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?

The description names a specific verb and resource: an explicit WRITE of a finished scene's last frame plus a graph connection into the following idle scene's first_frame slot. It is unmistakably a mutation of scene/graph state rather than a read or an execution start. It stops short of naming a sibling (e.g. materialize_last_frame, attach_result) to sharpen the boundary.

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?

"No payment or provider submit" implicitly scopes the tool away from execution/payment paths, and "same request_id replays the exact edit" tells the agent to reuse a request_id for retries. There is no explicit statement of when to prefer this over aimixer_canvas_attach_result or aimixer_canvas_materialize_last_frame, so routing between near-neighbors is left to inference.

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