Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Make a calibration print

make_calibration_print
Idempotent

Generate and slice calibration prints to tune filament temperature, flow, retraction, and first-layer settings.

Instructions

Generate and slice a calibration print for tuning a filament or the printer.

temperature_tower: one tower with a block per nozzle temperature, with the temperature changes written into the G-code. flow: one small cube per flow ratio. retraction: two towers per retraction length. first_layer: five single-layer squares across the bed to check levelling. Use it when a filament is new or prints look off and diagnose_print points to temperature, flow or retraction. Writes the G-code and .gcode.3mf files and returns their paths plus how to read the result.

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": {
      "kind": "<kind>"
    },
    "name": "make_calibration_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes'temperature_tower', 'flow', 'retraction' or 'first_layer'.
valuesNoValues to test: temperatures in °C, flow ratios, or retraction lengths in mm; at most 8. Default: a sensible range for the filament.
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.
filamentNoFilament preset to calibrate. Default: the selected filament.
output_dirNoFolder for the files. Default: Documents/Anycubic Slicer MCP/calibration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive, idempotent, closed-world writer, so the safety profile is covered. The description adds value beyond that by disclosing concrete side effects: it writes G-code and .gcode.3mf files, embeds temperature changes directly in the G-code, and returns file paths plus interpretation guidance. It stops short of noting runtime cost or that slicing requires the slicer context the defaults pull from.

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?

Front-loaded with a single clear purpose sentence, followed by a compact per-kind enumeration and a usage/return sentence. The kind breakdown is dense but every clause carries information an agent needs; no filler or repetition.

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 six-parameter file-writing tool with no output schema, the description covers the important unknowns: what files are produced, that temperature data is written into G-code, that paths are returned, and that interpretation guidance comes back. Combined with fully documented schema parameters, an agent has what it needs to call this correctly.

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 schema already documents all six parameters including defaults and the 8-value cap, which sets the baseline at 3. The description adds meaning by explaining what 'kind' produces in each case, implicitly telling the agent what the 'values' array should contain per kind, but it never restates units or limits itself.

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 ("Generate and slice a calibration print") and then enumerates the four supported kinds with the concrete artifact each produces (temperature tower with per-nozzle blocks, flow cubes, retraction towers, first-layer squares). This is specific enough that an agent can distinguish it from slicing/model tools in the sibling list 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the trigger condition ("when a filament is new or prints look off") and routes from a sibling ("diagnose_print points to temperature, flow or retraction"). The only gap is that 'first_layer' is offered as a kind but excluded from the stated trigger, so an agent must infer when to pick levelling.

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