Skip to main content
Glama
Sign In
bambu-printer-mcp

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

start_print_job

Start printing a G-code file already stored on a Bambu Lab printer. Specify the filename and printer model to begin the print job, ensuring correct model-specific start G-code.

Instructions

Start printing a G-code file already on the Bambu Lab printer

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": {
      "filename": "<filename>",
      "bambu_model": "<bambu_model>"
    },
    "name": "start_print_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
filenameYesName of the file to print
bambu_modelYesREQUIRED: Bambu Lab printer model. Ask the user if not known. Starting G-code for the wrong model can damage the printer.
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Changed1 schema field 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"
+]
  3. First observedv1.1.1

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already state that this is not read-only, not idempotent, open-world, and non-destructive. The description adds the useful precondition that the G-code file is already on the printer, but it does not disclose authentication requirements, printer-state requirements, whether the call blocks, or the physical consequences of starting a print.

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?

It is a single, front-loaded sentence with no filler. The key scope condition, 'already on the Bambu Lab printer,' appears immediately.

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?

The schema and annotations carry much of the burden, and the description establishes the core file-location precondition. However, for a physical print-start action with several similar sibling tools, it omits routing guidance and operational prerequisites that would make the definition more complete.

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 five parameters already have documented meaning, including the critical bambu_model warning. The description reinforces that filename refers to an existing G-code file but adds no parameter-specific syntax or constraints beyond the schema.

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: starting a print of a G-code file on a Bambu Lab printer. The phrase 'already on the printer' scopes it away from upload/print-file creation tools, though it does not explicitly distinguish this from the sibling tool 'start_print'.

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?

Usage is implied: the file must already exist on the printer. There is no explicit when-not guidance, no named alternative such as start_print or print_3mf, and no stated prerequisite that the printer be idle or correctly configured.

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