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

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_ams_drying

Idempotent

Start or stop the AMS filament drying cycle for a selected AMS unit, including AMS-HT id 128 on supported X2D setups.

Instructions

Start or stop the AMS filament drying cycle. X2D on macOS, or Linux with the native helper installed, uses the native official plug-in route and supports AMS-HT id 128.

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": {
      "action": "<action>",
      "ams_id": "<ams_id>"
    },
    "name": "set_ams_drying"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHostname or IP of the printer (default: value from env)
actionYesWhether to start or stop the drying cycle
ams_idYesAMS unit index from 0 to 3, or 128 for an X2D AMS-HT.
bambu_tokenNoAccess token (default: value from env)
bambu_serialNoSerial number (default: value from env)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.14
    • changedInput schema / properties / ams_id / description
      Previous value: -"AMS unit index from 0 to 3"New value: +"AMS unit index from 0 to 3, or 128 for an X2D AMS-HT."
  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?

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior. The description adds real value beyond that by disclosing platform-dependent routing (native plug-in on X2D macOS/Linux with helper) and the AMS-HT id 128 case, but says nothing about duration, whether the printer must be idle, or what happens on unsupported hosts.

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 sentences, with the core action front-loaded before the platform caveat. The second sentence is dense and slightly awkwardly phrased but carries non-redundant information.

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 two-required-parameter hardware mutation with full schema coverage and meaningful annotations, the description covers the action and the non-obvious platform/AMS-HT routing caveat. Remaining gaps (preconditions, failure modes) are modest but real.

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 coverage is 100%, so action enum, ams_id range, and credential defaults are already fully documented in the schema. The description's mention of AMS-HT id 128 merely repeats the schema, adding no new parameter meaning, so 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 first sentence gives a specific verb pair plus resource: it starts or stops the AMS filament drying cycle. No sibling tool in the list deals with drying, so differentiation is effectively inherent, though the description does not state that explicitly.

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 — an agent can infer it should be called when filament needs drying, but there is no statement of when to prefer it, prerequisites (e.g. AMS present, printer idle), or what to do on unsupported platforms.

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