Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_printer_filaments

Fetch live AMS and external filament inventory from Bambu Lab printers via MQTT, providing slot status, slicer profiles, and load recommendations for accurate print setup.

Instructions

Get the live AMS/external filament inventory from the printer over MQTT, including loaded/empty slot summary, resolved slicer profile paths, match confidence, and recommended load_filaments when the printer model is known.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoHostname or IP address of the printer (default: value from env)
bambu_modelNoOptional model hint used to resolve Bambu/Orca filament profile JSONs for each tray.
bambu_tokenNoAccess token for the Bambu Lab printer (default: value from env)
bambu_serialNoSerial number for the Bambu Lab printer (default: value from env)
nozzle_diameterNoOptional nozzle diameter used when resolving model-specific filament profile JSONs (default: 0.4).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.14
    • changedInput schema / properties / bambu_model / enum
      Previous value: -[
-  "p1s",
-  "p1p",
-  "p2s",
-  "x1c",
-  "x1e",
-  "a1",
-  "a1mini",
-  "h2d",
-  "h2s"
-]New value: +[
+  "p1s",
+  "p1p",
+  "p2s",
+  "x1c",
+  "x1e",
+  "a1",
+  "a1mini",
+  "h2d",
+  "h2s",
+  "h2c",
+  "x2d"
+]
  2. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations the description carries the full burden. It helpfully discloses that the data is live over MQTT and enumerates the returned content, but says nothing about failure modes, connectivity/auth needs (token, serial), or whether the call blocks or is read-only. Partial behavioral coverage only.

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 that leads with the core action and then lists the returned fields. Efficient, though the trailing enumeration of outputs makes it dense.

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 no output schema, the description does describe the return content, which is its main job here. However, it omits prerequisites (printer reachability, credentials) and any failure/error context, leaving gaps for a tool that talks to hardware over MQTT.

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 five parameters, giving a baseline of 3. The description adds minor value by linking bambu_model to the recommended load_filaments output, but adds no syntax or format detail beyond the schema.

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?

Specific verb (Get) plus resource (live AMS/external filament inventory) with the transport (MQTT) called out. It clearly distinguishes itself from siblings like get_printer_status or resolve_3mf_ams_slots by naming the filament inventory and the several derived outputs (slot summary, profile paths, match confidence, recommendations).

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 it reads, but the description never states when to reach for this tool versus alternatives such as get_printer_status, reread_ams_rfid, or resolve_3mf_ams_slots. No prerequisites or exclusions are given, so the agent must infer the routing.

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