Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

print_collar_charm

Prints a prepared two-part dog collar charm using fixed color mapping: inner part black on AMS 1, outer part white on AMS 2.

Instructions

Print a prepared two-part dog collar charm project using the fixed tray policy: inner/smaller object -> black on AMS 1 slot 1, outer/larger object -> white on AMS 2 slot 1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
bed_typeNoBed plate type currently installed (default: textured_plate)
timelapseNoEnable timelapse recording (default: false)
bambu_modelYesREQUIRED: Bambu Lab printer model. H2D, H2S, and H2C are the primary intended paths. X2D direct printing is not supported.
bambu_tokenNoAccess token (default: value from env)
source_pathNoPath to a prepared collar charm .3mf project or sliced 3MF. Required unless template_name is provided.
bambu_serialNoSerial number (default: value from env)
bed_levelingNoEnable auto bed leveling (default: true)
template_dirNoOptional template directory override when resolving template_name.
template_nameNoNamed collar charm template from the local registry. Required unless source_path is provided; resolves source_path automatically.
slicer_profileNoPath to the slicer profile/config file for auto-slicing (optional).
nozzle_diameterNoNozzle diameter in mm for auto-slicing (default: 0.4)
flow_calibrationNoEnable flow calibration (default: true)
vibration_calibrationNoEnable vibration calibration (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.14
    • removedInput schema / anyOf
      Removed value: -[
-  {
-    "required": [
-      "source_path",
-      "bambu_model"
-    ]
-  },
-  {
-    "required": [
-      "template_name",
-      "bambu_model"
-    ]
-  }
-]
    • changedInput schema / properties / bambu_model / description
      Previous value: -"REQUIRED: Bambu Lab printer model. H2D and H2S are the primary intended paths."New value: +"REQUIRED: Bambu Lab printer model. H2D, H2S, and H2C are the primary intended paths. X2D direct printing is not supported."
    • 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"
+]
    • changedInput schema / properties / source_path / description
      Previous value: -"Path to a prepared collar charm .3mf project or sliced 3MF."New value: +"Path to a prepared collar charm .3mf project or sliced 3MF. Required unless template_name is provided."
    • changedInput schema / properties / template_name / description
      Previous value: -"Named collar charm template from the local registry. Resolves source_path automatically."New value: +"Named collar charm template from the local registry. Required unless source_path is provided; resolves source_path automatically."
    • addedInput schema / required
      Added value: +[
+  "bambu_model"
+]
  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?

No annotations are provided, so the description carries the full burden. It usefully discloses the fixed AMS tray policy (inner->black AMS 1 slot 1, outer->white AMS 2 slot 1), which is genuine behavioral context absent from the schema, but it says nothing about prerequisites (pre-sliced vs raw), failure behavior, permissions, or whether it waits for completion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the action and the tray policy front-loaded, no filler, and every clause carrying information an agent needs.

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 14-parameter print tool with no annotations and no output schema, the definition covers the core action and tray policy but leaves the source_path/template_name requirement and printer-model constraints entirely to the schema. Adequate but with clear gaps given the tool's complexity.

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% across 14 parameters, so the schema already documents host, model, source_path, template_name, calibration flags, etc. The description adds no parameter-level meaning beyond hinting that the project must be 'prepared'. Baseline 3 is appropriate.

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?

States a specific verb (print) and resource (a prepared two-part dog collar charm project) plus the fixed tray policy, so an agent can tell it apart from the generic print_3mf siblings. However, it never names or contrasts the alternatives it overlaps with (print_3mf, start_print_job), so the differentiation is implicit rather than explicit.

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 phrase 'prepared two-part project' implies usage (use this for an already-prepared collar charm), but there is no explicit when-to-use, when-not-to-use, or routing to siblings like print_3mf or slice_with_template. Usage is left to inference.

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