Skip to main content
Glama

slice_with_template

Slices STL or 3MF files using a named template from the local registry, returning the output path plus per-plate time, weight, filament use, and slicer warnings for template-based workflows.

Instructions

Slice an STL or 3MF using a named template from the local registry. This is a higher-level wrapper around slice_stl for template-based workflows. Returns the same result: output_path plus per-plate time, weight, filament use and slicer warnings. Call preflight_check first.

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
scaleNoUniform scale factor.
orientNoAuto-orient model for optimal printability.
rotateNoZ-axis rotation in degrees.
arrangeNoAuto-arrange objects on the build plate.
bed_typeNoBed plate type for slicing (default: textured_plate). SuperTack is rejected for CLI slicing until the BambuStudio CLI identifier is verified.
min_saveNoProduce smaller output 3MF.
rotate_xNoX-axis rotation in degrees.
rotate_yNoY-axis rotation in degrees.
stl_pathYesPath to the STL or 3MF file to slice
bambu_modelYesREQUIRED: Bambu Lab printer model. Ask the user if not known. Using the wrong model can damage the printer.
bambu_tokenNoAccess token (default: value from env)
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).
repetitionsNoNumber of copies to print.
slice_plateNoWhich plate index to slice. 0 = all plates.
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. bambustudio exports a sliced 3MF.
bambu_serialNoSerial number (default: value from env)
template_dirNoOptional template directory override when resolving template_name.
ensure_on_bedNoLift floating models onto the bed.
template_nameYesNamed template from the local registry.
load_filamentsNoOverride filament profiles. Semicolon-separated paths to filament JSON configs.
slicer_profileNoExplicit slicer profile/config file. Overrides the named template only when provided in the tool call.
nozzle_diameterNoNozzle diameter in mm (default: 0.4)
filament_coloursNoOptional slot colours, one #RRGGBB per filament slot in order, separated by ';' (e.g. '#161616;#FFFFFF'). Defaults to the input 3MF's project colours, else the BambuStudio default.
project_settingsNo3MF input without a slicer profile or template: "keep" slices with the settings the project's creator saved (changed process settings, and each filament mapped to the bambu_model's equivalent preset); "printer_default" uses the printer's default process and filament. When omitted, the user is asked; if the client cannot ask, the call fails and you must ask the user, then pass this. The result's settings_report lists what was kept and not kept.
load_filament_idsNoOptional filament-to-object mapping string.
nozzle_volume_typeNoBambu-compatible slicing: the flow type of the nozzle installed on the printer (default: BAMBU_NOZZLE_VOLUME_TYPE, else standard). high_flow uses the presets' High Flow values, such as the filament's High Flow max volumetric speed, and is refused if the machine preset has no High Flow variant.
skip_modified_gcodesNoIgnore stale custom gcodes in the 3MF.
use_printer_filamentsNoDefault false. When true, a printer is configured, and no explicit slicer profile or load_filaments override is provided, replace the filaments with the printer's current or first loaded AMS filament.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.44

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that this wraps slice_stl, returns output_path plus per-plate time, weight, filament use and warnings, and requires preflight_check first, but it omits file-write side effects, auth/token needs, and failure behavior when a template is missing.

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?

Four short sentences, front-loaded with purpose and sibling relationship, followed by return shape and prerequisite. Every sentence carries useful information 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?

For a 30-parameter tool with no output schema and no annotations, the description supplies the return shape, wrapper relationship, and preflight prerequisite, while the highly detailed schema covers parameter specifics. It could still say more about template discovery and write behavior, so it is not fully complete.

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 nearly every parameter has a rich description, so the baseline is 3. The description only restates that template_name comes from the local registry and that the input is STL/3MF; it adds no parameter-level meaning beyond the schema.

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 an STL or 3MF using a named template from the local registry.' It explicitly positions itself as a higher-level wrapper around slice_stl for template-based workflows, which distinguishes it from the non-template slicing sibling.

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 says 'Call preflight_check first' and frames template-based workflows as its domain versus slice_stl. It does not mention list_templates as the way to discover template_name, so the guidance is clear but not fully exhaustive.

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