Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

slice_with_template

Slice STL or 3MF files using a named template from the local registry, reusing saved slicing settings to keep Bambu Lab print jobs consistent.

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

TableJSON 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.
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. 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"
+}
  2. 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."
  3. First observedv1.1.1

TDQS

A3.7/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 says nothing about side effects: with host, bambu_serial, bambu_token and print-related siblings present, it is unclear whether this only produces a sliced file or can also send a job to a printer, nor does it mention required permissions or reversibility. For a 28-parameter mutation-adjacent tool this is a significant gap.

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, zero waste, with the core action front-loaded and the sibling relationship placed second. Appropriately terse given that the schema carries the parameter detail.

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?

There is no output schema and no annotations, but the input schema is unusually rich (100% coverage, enums, defaults, embedded safety warnings), which supplies most of what an agent needs. The remaining gap is behavioral context around printing versus slicing-only, which the description does not resolve.

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 28 parameters thoroughly (enums, defaults, the printer-damage warning on bambu_model). The description only gestures at template_name via "a named template from the local registry" and adds no syntax, format, or interaction detail beyond the schema. Baseline 3 is correct.

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 (slice) and resource (STL or 3MF), and explicitly positions itself relative to a sibling by naming slice_stl as the lower-level primitive. An agent can distinguish the two tools 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 Guidelines4/5

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

"For template-based workflows" implies the condition that selects this tool over slice_stl, and the sibling is named. However there is no explicit when-not guidance (e.g. when to use slice_stl or the printer-side print tools instead).

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