bambu-printer-mcp

by rowbotik

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

start_print_job

Start printing a G-code file already on the Bambu Lab printer. Specify the filename to begin the job.

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

Input Schema

Name	Required	Description
`filename`	Yes	Name of the file to print
`host`	No	Hostname or IP of the printer (default: value from env)
`bambu_serial`	No	Serial number (default: value from env)
`bambu_token`	No	Access token (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jun 3, 2026

TDQS

B3/5.0

Behavior1/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action; it does not explain whether the tool waits for completion, returns immediately, what happens on errors (e.g., file not found), or if it requires the printer to be idle.

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 a single, concise sentence that efficiently conveys the core purpose without extraneous words.

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 no output schema and 4 parameters, the description lacks essential context: what happens after starting, how to monitor progress, error conditions, and interaction with printer state. More detail is needed for a print job tool.

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%: all parameters have descriptions. However, the description adds no new meaning beyond those schema descriptions. Baseline is 3.

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 action ('Start printing') and the resource ('G-code file already on the Bambu Lab printer'). It differentiates from sibling tools like 'print_3mf' (which likely slices first) and 'upload_gcode' (which only uploads).

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'print_3mf'). It does not mention prerequisites like the file must already be uploaded, or that it is intended for G-code files only.

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