Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Optimize multi-colour waste

optimize_multicolor
Idempotent

Measures filament waste from colour changes in multi-colour prints, tests settings that may reduce it, and recommends a change only when all colours survive and filament is saved.

Instructions

Measure how much filament a multi-colour print wastes on colour changes and try settings that might reduce it.

Recommends a setting only if every colour survives and it saves filament; otherwise says the default is best and gives layout tips such as fewer colour changes per layer. Slices several times, so it takes a while, and writes each test's G-code to output_dir. For single-colour prints use slice_model or compare_slices.

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>",
      "filaments": "<filaments>",
      "object_filaments": "<object_filaments>"
    },
    "name": "optimize_multicolor"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsYesModel paths, one per colour part, in the same order as object_filaments.
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.
filamentsYesFilament preset for each slot, e.g. two entries for a two-colour print.
output_dirNoFolder for the output files. Default: next to the first model.
output_nameNoBase name for the output files.
filament_coloursNo'#RRGGBB' for each slot; colour order affects how much is flushed.
object_filamentsYesFilament slot (1-based) for each model, e.g. [1, 2].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the tool slices several times, that this is slow, and that it writes each test's G-code into output_dir — real side effects an agent must anticipate. It stops short of saying how many iterations occur, whether existing files are overwritten, or roughly how long the run takes, so the cost profile is only qualitatively described.

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 tight sentences with no filler: what it measures, the recommendation rule, then runtime and file side effects, then the alternative. The most decision-relevant content is front-loaded and the exclusion guidance is placed last where it is easy to check before calling.

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?

For an 8-parameter, output-schema-less tool, the description covers purpose, decision logic, runtime cost, and file side effects. The main remaining gap is return-shape detail — whether measured waste figures are reported and in what form — though the recommendation outcome is described.

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 every parameter is already documented in the input schema, which sets the baseline at 3. The description only adds meaning for output_dir (test G-code is written there); it says nothing about models ordering, object_filaments, or filament_colours that the schema does not already cover.

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?

Names a specific verb and resource ('Measure how much filament a multi-colour print wastes on colour changes') plus the secondary action of trying alternative settings. It also distinguishes itself from siblings by directing single-colour work to slice_model or compare_slices, so the agent can route correctly without inspecting schemas.

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 scopes the tool to multi-colour prints and explicitly excludes single-colour use, naming two concrete alternatives. It also states the decision rule for when a recommendation is produced versus when the caller is told the default is best, which is the key guidance needed to interpret results.

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