Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

slice_with_template

Slice STL or 3MF models using a named template from the local registry to apply predefined print settings for consistent results.

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.

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 accepted only for pre-sliced print jobs 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). Printing compares it with the printer's reported nozzle.
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. Bambu-compatible choices (bambustudio, orcaslicer, orcaslicer-bambulab) export sliced 3MF; aliases such as fulu-orca and orca-studio are accepted.
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.
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. Printing compares it with the printer's reported nozzle flow.
skip_modified_gcodesNoIgnore stale custom gcodes in the 3MF.
use_printer_filamentsNoWhen true, and no explicit slicer profile or load_filaments override is provided, use the printer's current or first loaded AMS filament as the slicer filament profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.31
    • addedInput schema / properties / nozzle_volume_type
      Added value: +{
+  "description": "Bambu-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. Printing compares it with the printer's reported nozzle flow.",
+  "enum": [
+    "standard",
+    "high_flow"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / slicer_type / enum
      Previous value: -[
-  "bambustudio",
-  "orcaslicer",
-  "orcaslicer-bambulab",
-  "prusaslicer",
-  "cura",
-  "slic3r",
-  "fulu-orca",
-  "fulu-orcaslicer",
-  "orca-studio",
-  "orca-bambulab"
-]New value: +[
+  "bambustudio",
+  "orcaslicer",
+  "orcaslicer-bambulab",
+  "orca-slicer-api",
+  "prusaslicer",
+  "cura",
+  "slic3r",
+  "fulu-orca",
+  "fulu-orcaslicer",
+  "orca-studio",
+  "orca-bambulab"
+]
  2. Changed1 schema field changedv1.1.22
    • addedInput schema / properties / nozzle_type
      Added value: +{
+  "description": "Bambu-compatible slicing: the hotend nozzle material installed on the printer (default: BAMBU_NOZZLE_TYPE, else the model preset's stock nozzle, usually stainless_steel). Printing compares it with the printer's reported nozzle.",
+  "enum": [
+    "stainless_steel",
+    "hardened_steel",
+    "tungsten_carbide",
+    "brass"
+  ],
+  "type": "string"
+}
  3. Changed3 schema fields changedv1.1.14
    • changedInput schema / properties / bambu_model / enum
      Previous value: -[
-  "p1s",
-  "p1p",
-  "p2s",
-  "x1c",
-  "x1e",
-  "a1",
-  "a1mini",
-  "h2d",
-  "h2s"
-]New value: +[
+  "p1s",
+  "p1p",
+  "p2s",
+  "x1c",
+  "x1e",
+  "a1",
+  "a1mini",
+  "h2d",
+  "h2s",
+  "h2c",
+  "x2d"
+]
    • addedInput schema / properties / filament_colours
      Added value: +{
+  "description": "Optional 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.",
+  "type": "string"
+}
    • changedInput schema / properties / slicer_path / description
      Previous value: -"Path to the slicer executable (default: value from env)"New value: +"Path to the slicer executable (default: value from env). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."
  4. First observedv1.1.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions being a wrapper but does not disclose side effects, output file behavior, permissions, overwrite behavior, or what happens when template resolution fails.

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?

The description is two sentences, front-loaded with the primary action and followed by the key wrapper relationship. There is no wasted language.

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

Completeness2/5

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

This is a 29-parameter slicing tool with no annotations and no output schema, yet the description gives only a high-level wrapper summary. It leaves out important context about template resolution, generated outputs, and behavioral side effects needed for confident invocation.

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 parameter meanings are already fully documented in the schema. The description only reinforces that template_name comes from a local registry and does not add syntax or resolution details beyond that.

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?

The description states a specific verb and resource: slicing an STL or 3MF file using a named template. It distinguishes itself from sibling slice_stl by calling itself a higher-level wrapper for template-based workflows.

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?

It clearly positions the tool for template-based workflows and names slice_stl as the lower-level alternative. It does not explicitly say when not to use it or point users to list_templates for discovering template names.

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