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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_fan_speed

Idempotent

Control a Bambu printer's part, auxiliary, or chamber fan speed by percentage, with optional confirmation during active prints.

Instructions

Set a Bambu printer fan speed percentage. X2D on macOS, or Linux with the native helper installed, uses Bambu's networking plug-in without UI automation; other models use MQTT.

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": {
      "fan": "<fan>",
      "speed": "<speed>"
    },
    "name": "set_fan_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
fanYesFan to control: part, auxiliary, right_auxiliary, chamber, 1, 2, 3, or 10
hostNoHostname or IP of the printer (default: value from env)
speedYesFan speed percentage from 0 to 100
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)
confirm_during_printNoRequired for X2D fan changes while a print is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.14
    • addedInput schema / properties / confirm_during_print
      Added value: +{
+  "description": "Required for X2D fan changes while a print is running.",
+  "type": "boolean"
+}
    • changedInput schema / properties / fan / description
      Previous value: -"Fan to control: part, auxiliary, chamber, 1, 2, or 3"New value: +"Fan to control: part, auxiliary, right_auxiliary, chamber, 1, 2, 3, or 10"
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description adds genuine value beyond that by disclosing the transport mechanism (Bambu networking plug-in without UI automation on X2D/macOS or Linux-with-helper, MQTT otherwise), which helps diagnose failures. It stops short of covering the print-in-progress confirmation requirement or any auth/rate-limit behavior, so it is useful but not rich.

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?

Two sentences, front-loaded with the core action, and no filler. The platform/routing clause is dense but each part carries information; a slightly clearer separation of the two branches would improve readability.

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?

With six parameters, two required, full schema coverage, and annotations present, the definition is largely self-sufficient, and no output schema means return values need not be explained. However, for a hardware-mutating tool it omits what happens on failure, whether the change persists after a print, and the role of the confirm_during_print flag beyond the schema line.

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 six parameters including the fan enum-like list, speed range 0-100, and confirm_during_print are already documented in the schema. The description only restates that a percentage is set and adds no parameter-level detail, so the baseline of 3 applies.

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 first sentence gives a specific verb and resource ("Set a Bambu printer fan speed percentage"), which is enough to distinguish it from siblings like set_temperature, set_light, or set_print_speed. It does not explicitly name those siblings as alternatives, but the resource is unambiguous.

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 by the resource name rather than stated. The second sentence describes execution routing by model/platform, not when an agent should pick this tool over an alternative or what preconditions must hold (e.g., printer reachable, token present). No when-not guidance is given.

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