opentoonz-mcp

Overview Schema Source Related Servers Discussions Admin

Opentoonz Set Cells

opentoonz_set_cells

Place or replace animation cells at specific xsheet rows and columns by referencing existing levels, enabling precise scene exposure setup without manual sheet editing.

Instructions

Place/replace cells on a scene's xsheet.

placements: list of {"row": int, "col": int, "level": str, "fid": int|str}. Levels must already exist in the scene (see opentoonz_import_images_as_level). For the common animation task of holding each drawing for N frames, use opentoonz_exposure instead of computing rows yourself.

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": {
      "workspace": "<workspace>",
      "scene": "<scene>",
      "placements": "<placements>"
    },
    "name": "opentoonz_set_cells"
  }
}

Input Schema

Name	Required	Description	Default
`scene`	Yes
`workspace`	Yes
`placements`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Oct 17, 2026

TDQS

A4.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful precondition (levels must exist) and implies overwrite semantics via 'replace', but says nothing about what happens to pre-existing xsheet content at those rows, error behavior for a missing level, or required authorization.

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, zero filler, and the core operation is front-loaded before the placement schema and the routing note.

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?

An output schema exists, so return values need no prose, and the description covers the operation, the placement record shape, and the level precondition. Remaining gaps are minor: no explicit statement about overwriting existing cells or failure modes when a level or scene is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the placements array items are untyped objects (additionalProperties: true), so the description is the only source for the placement shape. It documents row/col/level/fid with types, which is substantial added value; only workspace/scene remain unexplained, though they are self-evident from siblings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Place/replace cells on a scene's xsheet') and names both a sibling to use instead (opentoonz_exposure) and one whose output it depends on (opentoonz_import_images_as_level). An agent can distinguish it from the other opentoonz_* tools without opening the schema.

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?

Gives an explicit conditional alternative: for the common 'hold each drawing for N frames' task, use opentoonz_exposure rather than computing rows manually. It also states the prerequisite that levels must already exist, pointing to the tool that creates them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.