Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_fan_speed

Set a Bambu 3D printer's fan speed percentage (0-100%) for part, auxiliary, or chamber cooling.

Instructions

Set a Bambu printer fan speed percentage. X2D on macOS uses the installed Bambu networking plug-in without UI automation; other models use MQTT.

Input Schema

TableJSON 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.2/5.0
Behavior3/5

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

No annotations are present, so the description bears the full behavioral burden. It does disclose genuinely useful context — X2D on macOS uses the networking plug-in without UI automation while other models use MQTT — but says nothing about failure behavior, reversibility, or the in-print confirmation flow (only the schema hints at it).

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 tight sentences with the core purpose front-loaded and no filler. The model-routing detail is relevant, though it slightly interrupts the primary statement.

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 a simple setter with no output schema, the description plus fully-covered schema give the agent enough to call it correctly. The model/macOS routing note covers the main behavioral quirk, though error and in-print confirmation behavior are only implied by the schema.

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 the schema already documents all six parameters including the enumerated fan choices and the confirm_during_print requirement. The description adds no parameter-level meaning beyond that, 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 (Set) and resource (Bambu printer fan speed percentage), clearly separating it from siblings like set_print_speed, set_temperature, and set_light. It stops short of explicitly contrasting with those siblings, 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 Guidelines2/5

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

The description never states when to reach for this tool versus related setters (set_print_speed, set_airduct_mode) or about preconditions for changing fan speed. The model-specific routing note implies context but does not give the agent an explicit use/avoid condition.

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