Skip to main content
Glama

print_3mf

Destructive

Sends a 3MF file to a specified Bambu Lab printer for printing, auto-slicing it when no G-code is present and applying the required model setting to prevent unsafe 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "three_mf_path": "<three_mf_path>",
      "bambu_model": "<bambu_model>"
    },
    "name": "print_3mf"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
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.
use_amsNoWhether to use the AMS (default: auto-detect from 3MF)
bed_typeNoBed plate type currently installed (default: textured_plate)
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. Use 254 for the external spool (on dual-nozzle printers: 254 = left/deputy nozzle external, 255 = right/main nozzle external). Expanded to project-level ams_mapping automatically from the 3MF's plate_N.json and gcode header.
timelapseNoEnable timelapse recording (default: false)
user_infoNoOptional BambuNetwork user_info JSON string passed to net.change_user for the FULU bridge.
ams_mappingNoProject-level AMS mapping array. Position = project filament index, value = absolute AMS tray. Positions the selected plate does not print are sent as -1, as Bambu Studio sends them, whatever is passed there (0-3=AMS 0, 4-7=AMS 1, 8-11=AMS 2, 128+=AMS-HT, 254=external, -1=unused). On dual-nozzle printers (H2D, H2D Pro, H2C, X2D) 254 is the LEFT/deputy nozzle external spool and 255 the RIGHT/main nozzle external spool, matching Bambu Studio's virtual tray ids; the gcode header's filament_map (1=left, 2=right) says which nozzle each filament was sliced for. Prefer ams_slots unless you know the project-level layout.
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_typeNoInstalled nozzle material, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_TYPE, else the preset's stock nozzle).
plate_indexNoZero-based plate index to print from the sliced 3MF (default: 0)
slicer_pathNoPath to the slicer executable for auto-slicing (default: value from env or a platform default). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
slicer_typeNoSlicer to use only if auto-slicing an unsliced 3MF. Bambu-compatible slicer aliases such as fulu-orca and orca-studio are accepted.
bambu_serialNoSerial number (default: value from env)
bed_levelingNoAuto bed leveling on or off. Omit to send what Bambu Studio's Send dialog would: the choice saved in BambuStudio.conf for this printer, else Studio's default.
country_codeNoBambuNetwork country code, such as US, used by the FULU bridge agent.
template_dirNoOptional template directory override when resolving template_name.
template_nameNoOptional named template from the local registry. Resolves to template_3mf_path automatically.
three_mf_pathYesPath to the 3MF file to print
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.
bridge_commandNoOverride command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.
slicer_profileNoPath to the slicer profile/config file for auto-slicing (optional).
try_emmc_printNoX2D native printing: true stores the job on internal storage (eMMC), false on the SD card or USB stick (refused unless the printer reports one ready). Omit to use the card when ready, else eMMC; X1C requires fresh advertised internal-printing support before using eMMC. BAMBU_NATIVE_TRY_EMMC_PRINT sets a server default.
connection_modeNoPrint path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in, storing the job on a ready SD card or USB stick, otherwise internal eMMC); X1C may opt in to bambu_native, for example when its firmware refuses FTPS uploads with 553; lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge.
connection_typeNoBambuNetwork connection type when connection_mode is bambu_network; cloud uses restored internet printing, lan uses local bridge printing.
nozzle_diameterNoNozzle diameter in mm for auto-slicing (default: 0.4)
pause_at_layersNoPause before each of these layers (1-based, as Bambu Studio and OrcaSlicer number them in the preview), for example to drop in magnets or nuts. The slicer writes the printer's own pause G-code there (M400 U1 on Bambu printers); the printer stops by itself and waits for Resume. Bambu Studio or OrcaSlicer CLI only. Used when the 3MF has no G-code yet; a sliced 3MF must already carry these pauses, or it is refused.
flow_calibrationNoFlow calibration task boolean. Omission resolves Studio settings (auto on P1/P1S); direct MQTT sends false for auto but does not transmit the integer auto mode. The result calibration report distinguishes resolved and transmitted options.
nozzle_diametersNoComplete per-nozzle diameters for a pre-sliced job, e.g. [0.4, 0.6]. Omit to verify its declared diameters against live telemetry; cannot combine with nozzle_diameter.
template_3mf_pathNoOptional template 3MF whose embedded Bambu slicer settings should be reused when auto-slicing this print job.
nozzle_volume_typeNoInstalled nozzle flow type, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_VOLUME_TYPE, else standard).
bambu_network_methodNoFULU print method when connection_mode is bambu_network; defaults to start_local_print for lan, and for cloud to Bambu Studio's order: start_local_print_with_record, then start_print if that fails.
vibration_calibrationNoVibration calibration (default false, as Bambu Studio sends).
bambu_network_config_dirNoConfig/log directory used by the FULU BambuNetwork agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.93
    • changedInput schema / properties / connection_mode / description
      Previous value: -"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in, storing the job on a ready SD card or USB stick, otherwise internal eMMC); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."New value: +"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in, storing the job on a ready SD card or USB stick, otherwise internal eMMC); X1C may opt in to bambu_native, for example when its firmware refuses FTPS uploads with 553; lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."
    • changedInput schema / properties / flow_calibration / description
      Previous value: -"Flow calibration on or off. Omit to send what Bambu Studio's Send dialog would (auto on P1/P1S)."New value: +"Flow calibration task boolean. Omission resolves Studio settings (auto on P1/P1S); direct MQTT sends false for auto but does not transmit the integer auto mode. The result calibration report distinguishes resolved and transmitted options."
    • changedInput schema / properties / try_emmc_print / description
      Previous value: -"X2D native printing: true stores the job on internal storage (eMMC), false on the SD card or USB stick (refused unless the printer reports one ready). Omit to use the card when ready, else eMMC; BAMBU_NATIVE_TRY_EMMC_PRINT sets a server default."New value: +"X2D native printing: true stores the job on internal storage (eMMC), false on the SD card or USB stick (refused unless the printer reports one ready). Omit to use the card when ready, else eMMC; X1C requires fresh advertised internal-printing support before using eMMC. BAMBU_NATIVE_TRY_EMMC_PRINT sets a server default."
  2. Changed1 schema field changedv1.1.77
    • changedInput schema / properties / ams_mapping / description
      Previous value: -"Project-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). On dual-nozzle printers (H2D, H2D Pro, H2C, X2D) 254 is the LEFT/deputy nozzle external spool and 255 the RIGHT/main nozzle external spool, matching Bambu Studio's virtual tray ids; the gcode header's filament_map (1=left, 2=right) says which nozzle each filament was sliced for. Prefer ams_slots unless you know the project-level layout."New value: +"Project-level AMS mapping array. Position = project filament index, value = absolute AMS tray. Positions the selected plate does not print are sent as -1, as Bambu Studio sends them, whatever is passed there (0-3=AMS 0, 4-7=AMS 1, 8-11=AMS 2, 128+=AMS-HT, 254=external, -1=unused). On dual-nozzle printers (H2D, H2D Pro, H2C, X2D) 254 is the LEFT/deputy nozzle external spool and 255 the RIGHT/main nozzle external spool, matching Bambu Studio's virtual tray ids; the gcode header's filament_map (1=left, 2=right) says which nozzle each filament was sliced for. Prefer ams_slots unless you know the project-level layout."
  3. Changed2 schema fields changedv1.1.61
    • changedInput schema / properties / bambu_network_method / description
      Previous value: -"FULU print method when connection_mode is bambu_network; defaults to start_print for cloud and start_local_print for lan."New value: +"FULU print method when connection_mode is bambu_network; defaults to start_local_print for lan, and for cloud to Bambu Studio's order: start_local_print_with_record, then start_print if that fails."
    • addedInput schema / properties / pause_at_layers
      Added value: +{
      +  "description": "Pause before each of these layers (1-based, as Bambu Studio and OrcaSlicer number them in the preview), for example to drop in magnets or nuts. The slicer writes the printer's own pause G-code there (M400 U1 on Bambu printers); the printer stops by itself and waits for Resume. Bambu Studio or OrcaSlicer CLI only. Used when the 3MF has no G-code yet; a sliced 3MF must already carry these pauses, or it is refused.",
      +  "items": {
      +    "minimum": 2,
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
  4. Changed3 schema fields changedv1.1.51
    • changedInput schema / properties / bed_leveling / description
      Previous value: -"Enable auto bed leveling (default: true)"New value: +"Auto bed leveling on or off. Omit to send what Bambu Studio's Send dialog would: the choice saved in BambuStudio.conf for this printer, else Studio's default."
    • changedInput schema / properties / flow_calibration / description
      Previous value: -"Enable flow calibration (default: true)"New value: +"Flow calibration on or off. Omit to send what Bambu Studio's Send dialog would (auto on P1/P1S)."
    • changedInput schema / properties / vibration_calibration / description
      Previous value: -"Enable vibration calibration (default: true)"New value: +"Vibration calibration (default false, as Bambu Studio sends)."
  5. Changed1 schema field changedv1.1.42
    • changedInput schema / properties / bambu_model / enum
      Previous value: -[
      -  "p1s",
      -  "p1p",
      -  "p2s",
      -  "x1c",
      -  "x1e",
      -  "a1",
      -  "a1mini",
      -  "h2d",
      -  "h2s",
      -  "h2c",
      -  "x2d"
      -]New value: +[
      +  "p1s",
      +  "p1p",
      +  "p2s",
      +  "x1c",
      +  "x1e",
      +  "a1",
      +  "a1mini",
      +  "h2d",
      +  "h2dpro",
      +  "h2s",
      +  "h2c",
      +  "x2d"
      +]
  6. Changed2 schema fields changedv1.1.32
    • changedInput schema / properties / connection_mode / description
      Previous value: -"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in and emmc tunnel); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."New value: +"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in, storing the job on a ready SD card or USB stick, otherwise internal eMMC); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."
    • addedInput schema / properties / try_emmc_print
      Added value: +{
      +  "description": "X2D native printing: true stores the job on internal storage (eMMC), false on the SD card or USB stick (refused unless the printer reports one ready). Omit to use the card when ready, else eMMC; BAMBU_NATIVE_TRY_EMMC_PRINT sets a server default.",
      +  "type": "boolean"
      +}
  7. Changed4 schema fields changedv1.1.31
    • changedInput schema / properties / ams_mapping / description
      Previous value: -"Project-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."New value: +"Project-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). On dual-nozzle printers (H2D, H2D Pro, H2C, X2D) 254 is the LEFT/deputy nozzle external spool and 255 the RIGHT/main nozzle external spool, matching Bambu Studio's virtual tray ids; the gcode header's filament_map (1=left, 2=right) says which nozzle each filament was sliced for. Prefer ams_slots unless you know the project-level layout."
    • changedInput schema / properties / ams_slots / description
      Previous value: -"Preferred 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."New value: +"Preferred 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. Use 254 for the external spool (on dual-nozzle printers: 254 = left/deputy nozzle external, 255 = right/main nozzle external). Expanded to project-level ams_mapping automatically from the 3MF's plate_N.json and gcode header."
    • addedInput schema / properties / nozzle_volume_type
      Added value: +{
      +  "description": "Installed nozzle flow type, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_VOLUME_TYPE, else standard).",
      +  "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"
      +]
  8. Changed1 schema field changedv1.1.22
    • addedInput schema / properties / nozzle_type
      Added value: +{
      +  "description": "Installed nozzle material, used when the 3MF must be auto-sliced (default: BAMBU_NOZZLE_TYPE, else the preset's stock nozzle).",
      +  "enum": [
      +    "stainless_steel",
      +    "hardened_steel",
      +    "tungsten_carbide",
      +    "brass"
      +  ],
      +  "type": "string"
      +}
  9. Changed6 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"
      +]
    • changedInput schema / properties / bridge_command / description
      Previous value: -"Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND."New value: +"Override command for the FULU bridge host or macOS/WSL wrapper; defaults to BAMBU_NETWORK_BRIDGE_COMMAND. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."
    • changedInput schema / properties / connection_mode / description
      Previous value: -"Print path to use: lan_mqtt_ftps uses this MCP's direct local MQTT/FTPS path; bambu_network uses the restored FULU BambuNetwork bridge."New value: +"Print path: bambu_connect hands a printable file to the signed-in Bambu Connect app for cloud-mode review; X2D otherwise defaults to bambu_native (Bambu Studio's installed local networking plug-in and emmc tunnel); lan_mqtt_ftps is the legacy direct MQTT/FTPS path; bambu_network uses the FULU bridge."
    • changedInput schema / properties / connection_mode / enum
      Previous value: -[
      -  "lan_mqtt_ftps",
      -  "bambu_network"
      -]New value: +[
      +  "lan_mqtt_ftps",
      +  "bambu_network",
      +  "bambu_native",
      +  "bambu_connect"
      +]
    • addedInput schema / properties / nozzle_diameters
      Added value: +{
      +  "description": "Complete per-nozzle diameters for a pre-sliced job, e.g. [0.4, 0.6]. Omit to verify its declared diameters against live telemetry; cannot combine with nozzle_diameter.",
      +  "items": {
      +    "enum": [
      +      0.2,
      +      0.4,
      +      0.6,
      +      0.8
      +    ],
      +    "type": "number"
      +  },
      +  "maxItems": 2,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / slicer_path / description
      Previous value: -"Path to the slicer executable for auto-slicing (default: value from env or a platform default)"New value: +"Path to the slicer executable for auto-slicing (default: value from env or a platform default). Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."
  10. First observedv1.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the agent knows this is a risky write operation. The description usefully adds that the tool auto-slices when the 3MF has no gcode, which implies a slicer subprocess may run, plus a safety warning tied to printer model. It says nothing about credentials, network prerequisites, failure modes, or that a physical print job is started.

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?

Three short sentences, front-loaded with the purpose, then behavior, then the safety constraint. Nothing is padded, though the IMPORTANT bambu_model sentence largely duplicates schema text rather than adding new information.

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?

For a destructive, open-world tool with 36 parameters, no output schema, and multiple connection modes, the description is thin. It does not explain what a successful call returns (job id, status), what happens when the printer is busy, or that credentials and host configuration come from environment defaults. The auto-slice and model-safety notes are the only substantive additions.

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 all 36 parameters are documented in the schema itself. The description repeats the bambu_model requirement and its damage warning almost verbatim from the schema, and adds no meaning to any other parameter. Baseline 3 applies when the schema does the heavy lifting.

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: 'Print a 3MF file on a Bambu Lab printer.' That is unambiguous. It does not, however, distinguish this tool from close siblings such as print_3mf_bambu_network, start_print, or start_print_job, so the agent must infer which entry point is appropriate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description never mentions the sibling print_3mf_bambu_network or explains when to pick this tool over start_print. The only directive is 'bambu_model must be specified', which is a required-parameter rule rather than routing guidance.

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