Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Slice a model

slice_model
Idempotent

Slices 3D models into printer-ready G-code for a single plate, returning print time, material use, cost, warnings, and output file paths.

Instructions

Slice 3D models into printer-ready G-code with Anycubic Slicer Next, running locally.

The main tool for a single plate. For several variants of one model use compare_slices; for a whole folder of parts use plan_project and slice_project. Writes .gcode and .gcode.3mf (send the .gcode.3mf to the printer) to output_dir, replacing files of the same name; takes seconds to a few minutes. Returns print time, grams, cost, layers, per-filament use, the output paths and slicer warnings, which flag overrides the slicer clamped or ignored. It never sends anything to a printer.

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": {
      "models": "<models>"
    },
    "name": "slice_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
plateNoWhich plate of a multi-plate 3MF to slice; 0 slices all plates.
scaleNoUniform scale factor, e.g. 25.4 for a model exported in inches. 0.01 to 100.
copiesNoCopies of each model on the plate, 1 to 200.
modelsYesPaths to STL, 3MF, OBJ or STEP files, all placed on one plate.
orientNoLet the slicer auto-orient parts. Prefer find_best_orientation plus rotation_deg.
arrangeNoLet the slicer arrange parts on the plate. Turn off to keep 3MF positions.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.
processNoProcess preset (layer height, speeds), e.g. '0.20mm Standard'. Omit to use the slicer window's selection.
bed_typeNoPlate type, e.g. 'Textured PEI Plate', 'Smooth PEI Plate', 'Cool Plate'. Default: the selected plate.
filamentsNoFilament preset names, one per filament slot, e.g. ['Anycubic PLA']. Omit to use the slicer window's selection.
overridesNoSetting key to value for this slice only, e.g. {'sparse_infill_density': '20%', 'wall_loops': 3, 'enable_support': true}. Keys come from get_preset.
timeout_sNoGive up after this many seconds, 30 to 7200.
output_dirNoFolder for the output files. Default: next to the first model.
output_nameNoBase name for the output files. Default: the first model's name.
rotation_degNoRotation in degrees applied before slicing, e.g. {'x': 90, 'y': 0, 'z': 0}.
filament_coloursNoMulti-colour: '#RRGGBB' for each filament slot, matching the loaded spools.
object_filamentsNoMulti-colour: filament slot (1-based) for each model, in order, e.g. [1, 2].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changedv0.3.1
    • addedInput schema / properties / arrange / description
      Added value: +"Let the slicer arrange parts on the plate. Turn off to keep 3MF positions."
    • addedInput schema / properties / bed_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Plate type, e.g. 'Textured PEI Plate', 'Smooth PEI Plate', 'Cool Plate'. Default: the selected plate.",
      +  "title": "Bed Type"
      +}
    • removedInput schema / properties / copies / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / copies / default
      Previous value: -nullNew value: +1
    • addedInput schema / properties / copies / description
      Added value: +"Copies of each model on the plate, 1 to 200."
    • addedInput schema / properties / copies / type
      Added value: +"integer"
    • addedInput schema / properties / filament_colours / description
      Added value: +"Multi-colour: '#RRGGBB' for each filament slot, matching the loaded spools."
    • addedInput schema / properties / filaments / description
      Added value: +"Filament preset names, one per filament slot, e.g. ['Anycubic PLA']. Omit to use the slicer window's selection."
    • addedInput schema / properties / models / description
      Added value: +"Paths to STL, 3MF, OBJ or STEP files, all placed on one plate."
    • addedInput schema / properties / object_filaments / description
      Added value: +"Multi-colour: filament slot (1-based) for each model, in order, e.g. [1, 2]."
    • addedInput schema / properties / orient / description
      Added value: +"Let the slicer auto-orient parts. Prefer find_best_orientation plus rotation_deg."
    • addedInput schema / properties / output_dir / description
      Added value: +"Folder for the output files. Default: next to the first model."
    • addedInput schema / properties / output_name / description
      Added value: +"Base name for the output files. Default: the first model's name."
    • addedInput schema / properties / overrides / description
      Added value: +"Setting key to value for this slice only, e.g. {'sparse_infill_density': '20%', 'wall_loops': 3, 'enable_support': true}. Keys come from get_preset."
    • addedInput schema / properties / plate / description
      Added value: +"Which plate of a multi-plate 3MF to slice; 0 slices all plates."
    • addedInput schema / properties / printer / description
      Added value: +"Printer preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window."
    • addedInput schema / properties / process / description
      Added value: +"Process preset (layer height, speeds), e.g. '0.20mm Standard'. Omit to use the slicer window's selection."
    • removedInput schema / properties / rotate_z
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "number"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Rotate Z"
      -}
    • addedInput schema / properties / rotation_deg
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Rotation in degrees applied before slicing, e.g. {'x': 90, 'y': 0, 'z': 0}.",
      +  "title": "Rotation Deg"
      +}
    • addedInput schema / properties / scale / description
      Added value: +"Uniform scale factor, e.g. 25.4 for a model exported in inches. 0.01 to 100."
    • addedInput schema / properties / timeout_s / description
      Added value: +"Give up after this many seconds, 30 to 7200."
    • removedInput schema / properties / use_project_settings
      Removed value: -{
      -  "default": false,
      -  "title": "Use Project Settings",
      -  "type": "boolean"
      -}
  2. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

Goes well beyond the annotations by disclosing side effects and runtime: it writes <name>.gcode and <name>.gcode.3mf to output_dir, replaces files of the same name, takes seconds to a few minutes, and never sends anything to a printer. The overwrite behavior is important context, though it sits in slight tension with destructiveHint=false; the description mitigates this by stating the replacement openly, so it is a caveat rather than a contradiction. It also enumerates the return payload (print time, grams, cost, layers, per-filament use, paths, clamped-override warnings), which fully covers tools with no annotations.

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?

Effectively three sentences: purpose, sibling routing, then effects and return values. The most decision-critical information (what it does, when to use a different tool) is front-loaded, and nothing is redundant given the size of the tool.

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

Completeness4/5

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

With 17 parameters and no output schema, the description carries real weight and does so: it names the artifacts produced, the runtime range, and the full returned metrics. Remaining gaps are minor (no explicit note that models is the only required input, no pagination/streaming concerns since none exist), so it is essentially complete for correct invocation.

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% and the schema already documents all 17 parameters with ranges, defaults and examples, so the baseline is 3. The description adds one genuinely useful fact not in the schema: that the .gcode.3mf file is the one to send to the printer, and that output_dir files are replaced by name. It does not otherwise explain parameters such as plate, scale or rotations.

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 resource ("Slice 3D models into printer-ready G-code with Anycubic Slicer Next, running locally") and immediately scopes itself as "The main tool for a single plate," which separates it from the batch-oriented siblings. An agent can identify what it does and what it does not do without opening the 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 routes the agent: use compare_slices for several variants of one model, plan_project plus slice_project for a whole folder of parts. Both alternatives are named with the condition that selects them, which is the strongest form of routing guidance.

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