Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Compare slices

compare_slices
Idempotent

Slice one model several ways and compare print time, filament use and cost side by side, revealing the price of stronger settings, finer layers or another orientation before you commit.

Instructions

Slice the same model several ways and compare print time, filament and cost side by side.

Use it to show the price of a choice (stronger settings, finer layers, another orientation) before committing; for a single slice use slice_model. Runs the slicer once per variant, so it takes longer, and writes each variant's G-code to output_dir. Returns each variant's numbers, the change against the first, and the fastest and lightest variant.

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

Input Schema

NameRequiredDescriptionDefault
modelsYesModel paths sliced the same way in every variant.
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.
variantsYesUp to 8 variants, each {'label': str, 'overrides': {...}, 'process': str, 'filaments': [...], 'rotation': {...}, 'scale': float}; all keys optional except label. The first is the reference.
filamentsNoFilament preset names, one per filament slot, e.g. ['Anycubic PLA']. Omit to use the slicer window's selection.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description goes beyond them by disclosing the cost profile ('runs the slicer once per variant, so it takes longer') and the filesystem side effect ('writes each variant's G-code to output_dir'), which explains why it is not read-only. The only unstated behavior is what happens to pre-existing files at output_dir (overwrite vs. new names), which keeps it below a 5.

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 front-loaded with purpose, then routing, then cost/side-effect/return summary; every clause carries information an agent needs and there is no filler.

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 no output schema, the description compensates by summarizing the return payload ('each variant's numbers, the change against the first, and the fastest and lightest variant') and by flagging the runtime and file-writing side effects. Minor gaps remain: the 8-variant cap and file overwrite behavior are only in the schema or unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all seven parameters and the baseline is 3. The description still adds meaning by illustrating what a variant can express ('stronger settings, finer layers, another orientation') and by confirming the output_dir side effect, going slightly beyond the schema text.

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 the same model several ways and compare print time, filament and cost side by side') and immediately contrasts scope with slice_model for the single-slice case, so an agent can tell the two apart 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?

Gives an explicit when-to-use scenario ('show the price of a choice ... before committing') and names the alternative tool plus the condition that selects it ('for a single slice use slice_model'). No exclusions are left to inference.

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