opentoonz-mcp

Overview Schema Source Related Servers Discussions Admin

Opentoonz Scene New

opentoonz_scene_new

Create or overwrite an empty OpenToonz scene in a selected workspace, optionally setting width, height, and FPS. Use it to start a project with the desired output resolution.

Instructions

Create (or overwrite) an empty scene, optionally setting its resolution.

The default camera is 1920x1080. Levels composite 1:1 and centred, so draw your art at the scene's size for full-frame output.

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

Input Schema

Name	Required	Default
`fps`	No
`scene`	No	main
`width`	No
`height`	No
`workspace`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Oct 17, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a key destructive trait: an existing scene may be overwritten. It also gives the default camera resolution (1920x1080) and compositing behavior (1:1, centred). It omits anything about required permissions or what happens to existing levels/cells on overwrite.

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?

Two compact sentences, front-loaded with the primary action, and the follow-up compositing note is genuinely useful context rather than filler. Nothing is redundant, though it is arguably too brief given the undocumented parameters.

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 needn't be explained. However, for a 5-parameter scene-creation tool with no annotations and 0% schema coverage, the description leaves most parameters and the overwrite consequences under-specified.

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 coverage is 0% for 5 parameters, so the description must compensate. It only gestures at resolution ('optionally setting its resolution'), leaving fps, the scene name (default 'main'), and the required workspace parameter entirely unexplained. This is a substantial gap over what the schema alone communicates.

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 ('Create ... an empty scene') plus the overwrite variant, so the operation is unambiguous. It does not explicitly differentiate itself from siblings like opentoonz_set_scene_settings or opentoonz_scene_info, so it falls short of a 5.

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?

Usage is only implied: 'Create (or overwrite)' hints this is the setup step that precedes drawing/rendering, but there is no explicit when-to-use versus set_scene_settings or when-not to use guidance. The overwrite caveat is useful but is behavioral rather than routing guidance.

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