Skip to main content
Glama

slice_with_template

Use a named template from the local registry to slice STL or 3MF files and prepare 3D print jobs for Bambu Lab printers.

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
stl_pathYesPath to the STL or 3MF file to slice
template_nameYesNamed template from the local registry.
template_dirNoOptional template directory override when resolving template_name.
bambu_modelYesREQUIRED: Bambu Lab printer model. Ask the user if not known. Using the wrong model can damage the printer.
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.
slicer_pathNoPath to the slicer executable (default: value from env)
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)
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.
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.
hostNoHostname or IP of the printer (default: value from env)
bambu_serialNoSerial number (default: value from env)
bambu_tokenNoAccess token (default: value from env)
load_filamentsNoOverride filament profiles. Semicolon-separated paths to filament JSON configs.
load_filament_idsNoOptional filament-to-object mapping string.
ensure_on_bedNoLift floating models onto the bed.
arrangeNoAuto-arrange objects on the build plate.
orientNoAuto-orient model for optimal printability.
repetitionsNoNumber of copies to print.
scaleNoUniform scale factor.
rotateNoZ-axis rotation in degrees.
rotate_xNoX-axis rotation in degrees.
rotate_yNoY-axis rotation in degrees.
min_saveNoProduce smaller output 3MF.
skip_modified_gcodesNoIgnore stale custom gcodes in the 3MF.
slice_plateNoWhich plate index to slice. 0 = all plates.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states it is a wrapper, but does not disclose behavioral traits like side effects, error cases, or what happens with templates.

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?

Two sentences with no wasted words; front-loads the core action and relationship to sibling tool. Minor improvement possible by adding quick usage hint.

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?

With 26 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return value, error behavior, or setup prerequisites, which a complex tool requires.

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 coverage is 100%, so baseline is 3. Description lists parameters but adds no additional meaning beyond the schema descriptions.

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?

The description uses specific verb+resource ('Slice an STL or 3MF') and clearly distinguishes itself from slice_stl as 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 Guidelines3/5

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

Implies usage for template-based workflows and mentions being a wrapper around slice_stl, but lacks explicit when-to-use or when-not-to-use guidance, especially compared to sibling slice_stl.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DMontgomery40/bambu-printer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server