Skip to main content
Glama

print_3mf

Send a 3MF file to a Bambu Lab printer for printing. Auto-slices unsliced files and requires specifying the printer model to prevent damage.

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.
connection_modeNoPrint path to use: lan_mqtt_ftps uses this MCP's direct local MQTT/FTPS path; bambu_network uses the restored FULU BambuNetwork bridge.
connection_typeNoBambuNetwork connection type when connection_mode is bambu_network; cloud uses restored internet printing, lan uses local bridge printing.
bambu_network_methodNoFULU print method when connection_mode is bambu_network; defaults to start_print for cloud and start_local_print for lan.
dev_idNoBambu device id for FULU BambuNetwork printing; defaults to BAMBU_DEV_ID or BAMBU_SERIAL.
dev_ipNoPrinter IP address for FULU BambuNetwork LAN/local print methods; defaults to host when provided.
bridge_commandNoOverride command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND.
bambu_network_config_dirNoConfig/log directory used by the FULU BambuNetwork agent.
country_codeNoBambuNetwork country code, such as US, used by the FULU bridge agent.
user_infoNoOptional BambuNetwork user_info JSON string passed to net.change_user for the FULU bridge.
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)
plate_indexNoZero-based plate index to print from the sliced 3MF (default: 0)
slicer_typeNoSlicer to use only if auto-slicing an unsliced 3MF. Bambu-compatible slicer aliases such as fulu-orca and orca-studio are accepted.
slicer_pathNoPath to the slicer executable for auto-slicing (default: value from env or a platform default)
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)
Behavior2/5

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

With no annotations, the description must carry full behavioral disclosure. It mentions auto-slicing and the importance of bambu_model, but omits side effects, error handling, prerequisites, and details about network modes. Important behavioral traits are missing.

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?

The description is concise (two sentences) and front-loaded with purpose. However, it could be structured to include more behavioral notes or a brief overview of connection modes without losing conciseness.

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 the tool's complexity (31 parameters, no output schema), the description is far too minimal. It does not explain what the tool returns, prerequisites, or how connection modes differ. Significant gaps remain.

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 parameter descriptions in the schema already document each parameter. The description only emphasizes bambu_model, adding minimal value. Baseline 3 is appropriate.

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 clearly states the tool prints a 3MF file on a Bambu Lab printer, and mentions auto-slicing. However, it does not differentiate from sibling tools like 'print_3mf_bambu_network', which appears to be a variant for a specific network mode.

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 is required for safety, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., print_3mf_bambu_network). Usage is implied but lacks exclusions.

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