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

Pencil2D Model Context Protocol (MCP) Server

by chriz-3656

pencil2d_add_frames_batch

Batch insert multiple animation keyframes into a Pencil2D project from a list or sorted image directory, with optional frame spacing, layer creation, and starting frame.

Instructions

Batch insert multiple animation keyframes into a project from a list or directory in a single operation.

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

Input Schema

NameRequiredDescriptionDefault
stepNoStep interval between frames (default 1).
framesNoList of keyframe objects to insert.
layer_nameNoTarget layer name when importing from directory.
start_frameNoStarting frame index when importing from directory (default 1).
project_pathYesPath to the .pclx file.
directory_pathNoOptional directory containing image frames to import in sorted order.
auto_create_layersNoAutomatically create bitmap layer if specified layer name does not exist (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / auto_create_layers
      Added value: +{
      +  "description": "Automatically create bitmap layer if specified layer name does not exist (default true).",
      +  "type": "boolean"
      +}
  2. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only implies a grouped write ('in a single operation') and says nothing about what happens to existing keyframes at the target indices, whether the operation is atomic on partial failure, or what permissions/locks are needed for the .pclx file.

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 no filler; the batch nature and the two input sources come first. It is efficiently sized for the amount of information conveyed, though it leaves the reader wanting the details it omits.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the high-level action but omits return/confirmation behavior, failure semantics, and the relationship between the directory-import parameters. The rich schema compensates for parameter details but not for behavioral completeness.

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 baseline is 3. The description adds the useful framing that keyframes come either 'from a list or directory', hinting at the frames vs directory_path modes, but it does not clarify that these are alternatives or how step/start_frame interact with each mode.

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 states a specific verb and resource ('batch insert multiple animation keyframes into a project') plus the two input modes ('from a list or directory'), which is enough to tell it apart from the single-frame sibling pencil2d_add_frame. It never names that sibling explicitly, so differentiation is implicit rather than stated.

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?

'Batch' and 'in a single operation' imply this is the multi-frame path versus pencil2d_add_frame, but the description never says when to prefer one over the other or when this tool is inappropriate. No prerequisites (e.g., project must exist, layer must exist) are given.

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