bambu-printer-mcp

Overview Schema Source Related Servers Discussions Admin

set_temperature

Idempotent

Set a checked bed or nozzle temperature for Bambu Lab printers, with positive heating requiring fresh telemetry and material and zero shutting the heater off.

Instructions

Set a checked bed or nozzle temperature. Positive heating requires matching fresh printer telemetry; nozzle heating also requires declared material. Zero turns the heater off.

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": {
      "component": "<component>",
      "temperature": "<temperature>"
    },
    "name": "set_temperature"
  }
}

Input Schema

Name	Required	Description
`host`	No	Hostname or IP of the printer (default: value from env)
`material`	No	Loaded material, for example PLA or PETG. Required for positive nozzle heating, including non-RFID spools.
`component`	Yes	Component to heat: bed, nozzle, or extruder
`bambu_model`	No	Printer model, required for positive heating unless configured in the environment
`bambu_token`	No	Access token (default: value from env)
`temperature`	Yes	Finite target temperature in °C, checked against model/component and declared material limits
`bambu_serial`	No	Serial number (default: value from env)
`nozzle_diameter`	No	Installed nozzle diameter to compare with printer-reported configuration (default 0.4)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.42Oct 31, 2026

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"
+]

Changed5 schema fields changedv1.1.14Sep 29, 2026

addedInput schema / properties / bambu_model

Added value: +{
+  "description": "Printer model, required for positive heating unless configured in the environment",
+  "enum": [
+    "p1s",
+    "p1p",
+    "p2s",
+    "x1c",
+    "x1e",
+    "a1",
+    "a1mini",
+    "h2d",
+    "h2s",
+    "h2c",
+    "x2d"
+  ],
+  "type": "string"
+}

addedInput schema / properties / material

Added value: +{
+  "description": "Loaded material, for example PLA or PETG. Required for positive nozzle heating, including non-RFID spools.",
+  "type": "string"
+}

addedInput schema / properties / nozzle_diameter

Added value: +{
+  "description": "Installed nozzle diameter to compare with printer-reported configuration (default 0.4)",
+  "enum": [
+    0.2,
+    0.4,
+    0.6,
+    0.8
+  ],
+  "type": "number"
+}

changedInput schema / properties / temperature / description

Previous value: -"Target temperature in °C"New value: +"Finite target temperature in °C, checked against model/component and declared material limits"

addedInput schema / properties / temperature / minimum
```
Added value: +0
```

First observedv1.1.1May 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint=false, idempotentHint=true and destructiveHint=false, the description adds real behavioral value: it discloses the telemetry and material gating that must be satisfied before the device will heat, and that a zero target is an off-switch. What it omits is whether the call blocks until temperature is reached or returns immediately, and how a rejected request surfaces (error vs. silent no-op).

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?

Three short sentences, zero padding. The core action is front-loaded, followed by preconditions and then the off case, which is the right information order for an agent deciding whether it can safely call this.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation with a full schema and no output schema, the description covers the essentials: what it changes, the safety gates, and the off case. It stops short of describing the response or timing behavior, which is the one thing an agent might still need to know before chaining a follow-up print call.

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 every parameter is already documented in the schema, including the material requirement for positive nozzle heating and the zero semantics of temperature. The description restates those relationships at the call level but adds no syntax, unit, or default information beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Set') and resource ('bed or nozzle temperature') and immediately scopes what that means via 'Positive heating... / Zero turns the heater off.' No sibling in the list sets temperature, so there is no ambiguity to resolve, and an agent can tell exactly what this does.

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

Usage Guidelines4/5

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

Gives clear when-to-use context in the form of preconditions: positive heating needs fresh telemetry, and nozzle heating additionally needs a declared material. It also carves out the zero case. It does not name an alternative tool or give guidance on when not to heat at all, which keeps it at 4 rather than 5.

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

Deploy Server