opentoonz-mcp

Overview Schema Source Related Servers Discussions Admin

Opentoonz Render

opentoonz_render

Render an OpenToonz scene to PNG frames in /render/ using tcomposer. Specify start and end frames to render only a section and reduce render cost.

Instructions

Render a scene to PNG frames under /render/ with tcomposer.

By default the whole scene renders. Give start and end together to render an inclusive frame range instead — e.g. start=1, end=3 for frames 1-3 — which is much cheaper when you only need a section.

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

Input Schema

Name	Required	Default
`end`	No
`scene`	Yes
`start`	No
`out_name`	No	render
`workspace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Oct 17, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden. It discloses the output path and that ranges are cheaper, but doesn't state whether rendering mutates existing files, requires a valid workspace/scene to exist, or what happens on error. Adds some useful behavior (cost of full-scene render) but leaves key operational traits uncovered.

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?

Front-loaded with the core action and output target, then a compact second sentence on range behavior. Two sentences, zero padding, every clause earns its place.

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 5-parameter tool with 0% schema coverage and no output schema, the description is thin: it omits the meaning of workspace, scene, and out_name. It does convey the core render-range use case, but an agent would lack the parameter context needed to call it confidently.

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 0% and none of the parameters have descriptions in the schema, so the description must compensate. It explains start/end semantics (inclusive range, must be given together) but says nothing about workspace, scene, or out_name — out_name silently defaults to 'render' and its effect on the output path is never clarified.

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 (Render) and resource (scene to PNG frames) plus the output location and tool (tcomposer). It distinguishes itself from render_video, render_gif, and render_frame, but doesn't explicitly name them or clarify the PNG-vs-video boundary, which is the key sibling distinction.

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?

Explains the default range behavior (whole scene) and the cheaper alternative (start+end together), which is useful when-to-use guidance. However, it doesn't address when to prefer render_frame, render_video, render_gif, or render_batch over this tool.

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