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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_print_speed

Idempotent

Switch a Bambu Lab 3D printer between silent, standard, sport, and ludicrous speed modes to control print time versus quality.

Instructions

Set the active print speed mode: silent, standard, sport, or ludicrous.

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": {
      "mode": "<mode>"
    },
    "name": "set_print_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
modeYesSpeed mode to apply: silent/1, standard/2, sport/3, or ludicrous/4
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent, open-world operation, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the change can be applied during an active print, whether it persists across jobs, or how it interacts with the current job. No contradiction with annotations.

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?

A single front-loaded sentence naming the action and its valid values, with zero filler. It could be improved only by appending the operational context that is currently missing, but nothing present is wasteful.

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?

For a simple four-parameter setter with full schema coverage, annotations, and no output schema, the description is minimally sufficient to invoke the tool correctly. It is incomplete regarding the effect on a running job and persistence, which matters for a print-speed mutation.

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 four parameters (host, mode, token, serial) are documented in the schema, including the numeric aliases 1-4 for modes. The description merely repeats the human-readable mode names already present in the enum, adding no syntax or format detail beyond the schema; baseline 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 description gives a specific verb ('Set') and resource ('active print speed mode') and enumerates the four named modes, so the agent knows exactly what the tool changes. It does not distinguish itself from adjacent setters like set_fan_speed or set_temperature, 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 only implied: it is clearly a setter for a printer speed preset, but the description never says when to use it (e.g. mid-print vs. idle), nor does it mention prerequisites or alternatives. There is no explicit when-not guidance.

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