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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cancel_print

DestructiveIdempotent

Stops the current 3D print job on a Bambu Lab printer, letting you halt a running print through printer controls and prevent further unwanted filament use.

Instructions

Cancel the current print job on the Bambu Lab printer

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)
connection_modeNoThe connection the print used. Defaults to BAMBU_DEFAULT_CONNECTION_MODE, the same default print_3mf uses, else the model's route.
connection_typeNoFULU BambuNetwork connection type the print used. Defaults to BAMBU_DEFAULT_CONNECTION_TYPE, as for print_3mf. Authenticated controls support lan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.61
    • addedInput schema / properties / connection_mode
      Added value: +{
+  "description": "The connection the print used. Defaults to BAMBU_DEFAULT_CONNECTION_MODE, the same default print_3mf uses, else the model's route.",
+  "enum": [
+    "lan_mqtt_ftps",
+    "bambu_network",
+    "bambu_native"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / connection_type
      Added value: +{
+  "description": "FULU BambuNetwork connection type the print used. Defaults to BAMBU_DEFAULT_CONNECTION_TYPE, as for print_3mf. Authenticated controls support lan.",
+  "enum": [
+    "lan",
+    "cloud"
+  ],
+  "type": "string"
+}
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the agent knows this terminates a job irreversibly. The description adds only the scoping detail that it targets the current job, and says nothing about post-cancel state, permission needs, or failure when no job is running.

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 with no filler, correctly identifying the target resource first. It is efficient, though the brevity leaves room that could have been used for routing guidance rather than padding.

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 zero-required-parameter cancel action with complete schema descriptions and annotations covering the destructive/idempotent profile, the description supplies enough to call it correctly. The only gap is the absence of any note about what happens to the job or printer afterwards.

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% and all five parameters are optional with defaults from environment variables, so the schema carries the full semantics. The description adds no additional meaning about connection_mode or connection_type, which matters since the cancel presumably must use the same route as the original print.

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 states a specific verb and resource ('Cancel the current print job') plus the target platform ('Bambu Lab printer'), which immediately separates it from pause_print, resume_print, and start_print_job. It stops short of naming which sibling to use instead when the intent is merely to suspend work.

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?

The word 'current' implies this applies only to the active job, giving some implicit usage context. There is no explicit when-to-use versus when-to-pause guidance, and no mention of prerequisites such as an in-progress job being required for a meaningful call.

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