Skip to main content
Glama
DMontgomery40

MCP 3D Printer Server

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

slice_with_template

Slice an STL or 3MF using a named process template from the local registry, with machine presets taken from the selected Bambu model and nozzle diameter.

Instructions

Slice an STL or 3MF with a named template from the local template registry (BAMBU_TEMPLATE_DIR). The template supplies process settings; the machine preset still comes from bambu_model and nozzle_diameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNoBambu-compatible slicing: uniform scale factor applied before slicing (1.0 = original size).
orientNoBambu-compatible slicing: auto-orient for printability (--orient).
rotateNoBambu-compatible slicing: Z-axis rotation in degrees before slicing.
arrangeNoBambu-compatible slicing: auto-arrange objects on the plate (--arrange). Set false to keep an existing layout.
bed_typeNoBambu-compatible slicing: build plate type (default: BED_TYPE or textured_plate).
min_saveNoBambu-compatible slicing: write a smaller output 3MF (--min-save).
rotate_xNoBambu-compatible slicing: X-axis rotation in degrees before slicing.
rotate_yNoBambu-compatible slicing: Y-axis rotation in degrees before slicing.
stl_pathYesPath to the STL or 3MF file to slice
uptodateNoBambu-compatible slicing: refresh 3MF preset configs to the installed slicer version (--uptodate).
bambu_modelNoBambu Lab printer model. Required for bambustudio and orcaslicer-bambulab (elicited or read from BAMBU_MODEL when omitted); passing it with orcaslicer selects the Bambu-compatible path. The installed slicer must contain the exact model/nozzle preset.
nozzle_typeNoBambu-compatible slicing: the hotend nozzle material installed on the printer (default: BAMBU_NOZZLE_TYPE, else the model preset's stock nozzle, usually stainless_steel; X1C/X1E presets use hardened_steel). Printing compares it with the printer's reported nozzle.
repetitionsNoBambu-compatible slicing: print N identical copies (--repetitions).
slice_plateNoBambu-compatible slicing: plate number to slice; 0 slices all plates (default).
slicer_pathNoPath to the slicer executable (default: value from env). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
slicer_typeNoType of slicer to use (prusaslicer, cura, slic3r, orcaslicer, orcaslicer-bambulab, bambustudio). Use orcaslicer-bambulab for the FULU fork. bambustudio and orcaslicer-bambulab (and orcaslicer with bambu_model) export a sliced 3MF.
skip_objectsNoBambu-compatible slicing: comma-separated object indices to skip, e.g. '3,5,10'.
template_dirNoTemplate directory override when resolving template_name (default: BAMBU_TEMPLATE_DIR or ~/Sync/bambu/templates).
clone_objectsNoBambu-compatible slicing: comma-separated clone counts per object index, e.g. '1,3,1,10'.
ensure_on_bedNoBambu-compatible slicing: lower floating models onto the bed (--ensure-on-bed).
template_nameYesNamed template from the local registry (required).
allow_mix_tempNoBambu-compatible slicing: allow filaments with different temperature requirements on one plate.
load_filamentsNoBambu-compatible slicing: filament profile JSON paths in slot order, ';'-separated. One profile applies to every project slot; otherwise supply one per slot.
slicer_profileNoExplicit process profile that overrides the named template only when provided in this call.
nozzle_diameterNoNozzle diameter in mm (default: NOZZLE_DIAMETER or 0.4). Selects the '<model> <diameter> nozzle' machine preset.
enable_timelapseNoBambu-compatible slicing: insert timelapse parking moves (--enable-timelapse).
filament_coloursNoBambu-compatible slicing: one #RRGGBB per filament slot, ';'-separated. Defaults to the input 3MF's colours, then each profile's colour.
filament_profileNoFilament profile path(s), ';'-separated in slot order, loaded with --load-filaments (default: FILAMENT_PROFILE/SLICER_FILAMENT_PROFILE env). Alias of load_filaments.
load_filament_idsNoBambu-compatible slicing: comma-separated filament IDs mapping load_filaments to objects, e.g. '1,2,3,1'.
template_3mf_pathNoBambu-compatible slicing: 3MF or profile whose embedded slicer settings are reused as the process profile (default: BAMBU_TEMPLATE_3MF_PATH). An explicit slicer_profile takes precedence.
skip_modified_gcodesNoBambu-compatible slicing: ignore custom G-code embedded in an input 3MF (--skip-modified-gcodes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals that the template registry is resolved from BAMBU_TEMPLATE_DIR and that machine settings come from separate parameters, but says nothing about the output artifact, write location, or failure behavior of a slicing run.

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?

Two sentences, front-loaded with the core action and scope, then the settings-precedence detail. No filler, no repetition of enum values or defaults already in the schema.

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

Completeness3/5

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

For a 31-parameter tool with no output schema, the description is lean but leaves gaps: it does not say what is produced (sliced 3MF vs G-code), where it is written, or how a missing/invalid template is surfaced. The rich schema compensates for most parameter ambiguity, so this is adequate but not complete.

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 description coverage is 100%, so the parameters are already documented and the baseline is 3. The description goes slightly beyond the schema by clarifying the interaction between template_name, bambu_model, and nozzle_diameter — non-obvious precedence that the per-parameter schema text does not state jointly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Slice) plus resource (STL or 3MF) and the distinguishing mechanism (a named template from the local template registry). This separates it conceptually from the sibling slice_stl, though it never names that sibling or list_templates/save_template, so the contrast is implied rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The second sentence explains the division of labor (template supplies process settings; machine preset comes from bambu_model and nozzle_diameter), which implies when this tool is appropriate. However there is no explicit 'use this instead of slice_stl when...' guidance or note about what happens when the template name is not found.

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

Deploy Server

Other Tools