Skip to main content
Glama
rowbotik

bambu-printer-mcp

print_3mf

Print a 3MF file on a Bambu Lab printer. Auto-slices if the file lacks gcode; specify printer model for safe operation.

Instructions

Print a 3MF file on a Bambu Lab printer. Auto-slices if the 3MF has no gcode. IMPORTANT: bambu_model must be specified to ensure safe printer operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
three_mf_pathYesPath to the 3MF file to print
bambu_modelYesREQUIRED: Bambu Lab printer model. Ask the user if not known. Using the wrong model can damage the printer.
bed_typeNoBed plate type currently installed (default: textured_plate)
hostNoHostname or IP of the printer (default: value from env)
bambu_serialNoSerial number (default: value from env)
bambu_tokenNoAccess token (default: value from env)
use_amsNoWhether to use the AMS (default: auto-detect from 3MF)
ams_mappingNoProject-level AMS mapping array. Position = project filament index, value = absolute AMS tray (0-3=AMS 0, 4-7=AMS 1, 8-11=AMS 2, 128+=AMS-HT, 254=external, -1=unused). Prefer ams_slots unless you know the project-level layout.
ams_slotsNoPreferred AMS input: one absolute tray index per USED filament in plate order, e.g. [1] for a single-filament print pulling from AMS 0 slot 1. Expanded to project-level ams_mapping automatically from the 3MF's plate_N.json and gcode header.
auto_match_amsNoWhen true, match the sliced 3MF's tray_info_idx requirements against live AMS inventory and use the resulting ams_slots. Ignored when ams_mapping or ams_slots is provided.
bed_levelingNoEnable auto bed leveling (default: true)
flow_calibrationNoEnable flow calibration (default: true)
vibration_calibrationNoEnable vibration calibration (default: true)
timelapseNoEnable timelapse recording (default: false)
slicer_profileNoPath to the slicer profile/config file for auto-slicing (optional).
template_3mf_pathNoOptional template 3MF whose embedded Bambu slicer settings should be reused when auto-slicing this print job.
template_nameNoOptional named template from the local registry. Resolves to template_3mf_path automatically.
template_dirNoOptional template directory override when resolving template_name.
nozzle_diameterNoNozzle diameter in mm for auto-slicing (default: 0.4)
Behavior3/5

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

Without annotations, the description carries full burden. It discloses auto-slicing and the safety criticality of bambu_model, but omits behaviors like print queue handling, error responses, or whether the call is blocking.

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 core action and critical requirement. Every word is meaningful and avoids redundancy.

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?

Given 19 parameters, no output schema, and no annotations, the description is minimal. It lacks details on return values, potential errors, prerequisites like printer connectivity, or workflow steps, making it insufficient for safe 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 the schema already documents all parameters. The description adds value with the safety warning about bambu_model and the auto-slicing note, but does not go beyond what is in 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?

The description clearly states the tool prints a 3MF file on a Bambu Lab printer and auto-slices if needed. It distinguishes from siblings like upload_file or slice_stl by specifying the direct print action.

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 description emphasizes that bambu_model must be specified for safety, giving a condition for use. However, it does not provide when-not-to-use guidance or mention alternatives like upload_gcode for pre-sliced files.

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/rowbotik/bambu-printer-mcp'

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