Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Animate layers

animate_layers
Idempotent

Creates an animated GIF from a G-code file showing the print building layer by layer, so users can watch or share the build progress. Saves the GIF next to the G-code.

Instructions

Make an animated GIF of the print building up layer by layer.

Use it when the user wants to watch the build or share it; for checking one layer use preview_gcode instead. Writes _layers.gif next to the G-code, replacing an older one. Returns the GIF and its path.

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": {
      "path": "<path>"
    },
    "name": "animate_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a .gcode file on this computer, e.g. one written by slice_model.
sizeNoFrame size in pixels, 200 to 1000.
max_framesNoMost frames in the GIF, 5 to 200; layers are skipped evenly to fit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses the concrete side effect: a file named <name>_layers.gif is written next to the G-code and replaces an older one, and it states the return value (the GIF and its path). That is meaningful disclosure the annotations do not carry, since readOnlyHint=false alone doesn't say what is written or that it overwrites. Only minor gaps remain, such as render cost/time for large models.

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, each doing distinct work: what it makes, when to choose it, and its side effects and return. The purpose is front-loaded and there is no redundant restatement of the title or schema.

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

Completeness5/5

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

For a three-parameter tool with no output schema, the definition covers purpose, routing, output artifact, overwrite behavior, and return value. Nothing an agent needs to invoke it correctly is missing.

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 path, size, and max_frames are already fully documented, including the even layer-skipping behavior. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 and artifact ('Make an animated GIF') plus the exact subject ('the print building up layer by layer'), so the agent knows precisely what is produced. It also names the sibling it is not (preview_gcode), making disambiguation possible without opening either 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?

Explicitly gives the when-to-use condition ('user wants to watch the build or share it') and the when-not condition routed to a named alternative ('for checking one layer use preview_gcode instead'). Nothing about selection is left to inference.

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