Skip to main content
Glama
Pencil2D Model Context Protocol (MCP) Server

Pencil2D Model Context Protocol (MCP) Server

by chriz-3656

pencil2d_export

Render Pencil2D .pclx projects to MP4, animated GIF, or image sequences for preview, delivery, or frame-by-frame export.

Instructions

Render a Pencil2D animation project to video (MP4), animated GIF, or image sequence using the Pencil2D AppImage CLI.

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_path": "<project_path>",
      "output_path": "<output_path>"
    },
    "name": "pencil2d_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoFramerate override for export.
widthNoOptional output width in pixels.
cameraNoName of camera layer to use.
heightNoOptional output height in pixels.
timeoutNoExport execution timeout in seconds (default 180).
end_frameNoLast frame to include in export.
output_pathYesOutput rendered file (e.g., animation.mp4, preview.gif, frames.png).
start_frameNoFirst frame to include in export.
project_pathYesPath to the .pclx file.
transparencyNoEnable transparency when exporting images or formats that support it.
force_pure_pythonNoForce using internal pure-Python compositor without invoking AppImage CLI (supports GIF, PNG sequence, MP4 via ffmpeg).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • addedInput schema / properties / force_pure_python
      Added value: +{
      +  "description": "Force using internal pure-Python compositor without invoking AppImage CLI (supports GIF, PNG sequence, MP4 via ffmpeg).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fps
      Added value: +{
      +  "description": "Framerate override for export.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / timeout
      Added value: +{
      +  "description": "Export execution timeout in seconds (default 180).",
      +  "type": "integer"
      +}
  2. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the execution backend (Pencil2D AppImage CLI) and the supported formats, but omits whether existing output files are overwritten, what happens on timeout/failure, and what external dependencies must be present. It adds real context yet leaves significant behavioral gaps for a mutation-style tool.

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?

A single front-loaded sentence with zero filler that states the action, resource, outputs, and backend. It is efficient, though for an 11-parameter tool the extreme brevity leaves no room for the guidance the definition lacks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, no annotations, and no output schema, the definition should explain return behavior (e.g., resulting file path or status), overwrite semantics, and the AppImage/ffmpeg dependency implied by force_pure_python. None of this is present, so an agent cannot fully predict the outcome of a call.

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 description coverage is 100%, so the schema already documents all 11 parameters, including start_frame/end_frame, fps, camera, and force_pure_python. The description only loosely ties the format list to output_path and adds no syntax or behavioral meaning beyond the schema, so the baseline 3 applies.

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 ('Render') and resource ('Pencil2D animation project') and enumerates the output formats (MP4, GIF, image sequence), which clearly separates it from siblings like pencil2d_extract_frames or pencil2d_create_spritesheet. It stops short of explicitly naming those alternatives, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus pencil2d_extract_frames (also produces images) or pencil2d_create_spritesheet. No prerequisites, no exclusions, and no guidance on choosing an output format are given; usage is only implied by the verb.

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