Skip to main content
Glama

ams_filament_drying

Start or stop an AMS 2 Pro / AMS HT active dry cycle.

Instructions

Start or stop an AMS 2 Pro / AMS HT active dry cycle.

Bambu printers with an AMS 2 Pro or AMS HT dry filament in place.
This controls that dryer.

To START (``mode=1``): set ``temp_c`` (drying temperature),
``duration_min`` (> 0), and ``cooling_temp_c`` -- which must be
>= 45, or the printer silently ignores the command.  A start is
checked against the unit's own ceiling (AMS 2 Pro 65 C, AMS HT 85 C)
before it is sent; when Kiln cannot run that check, nothing is sent and
the answer says why.  To STOP (``mode=0``): only ``ams_id`` is needed,
and a stop is always sent.

Only Bambu printers with an AMS 2 Pro / AMS HT support this; other
printers and plain AMS / AMS Lite units return an error.

:param ams_id: AMS unit index (0-based).
:param mode: 1 to start drying, 0 to stop.
:param duration_min: Dry-cycle length in minutes (> 0 to start).
:param temp_c: Drying temperature in C (required to start; capped
    at the unit's max -- AMS 2 Pro 65 C, AMS HT 85 C).
:param cooling_temp_c: Cooldown temperature in C (>= 45 to start).
:param humidity: Optional target humidity.
:param rotate_tray: Optional tray-rotation flag.
:param printer_name: Target printer.  Omit for the default printer.
:returns: Dict with the dispatched command and a status message.

Input Schema

NameRequiredDescriptionDefault
modeYes
ams_idYes
temp_cNo
humidityNo
rotate_trayNo
duration_minNoDefault: 0.
printer_nameNo
cooling_temp_cNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses silent-failure semantics (values below 45 are silently ignored by the printer), pre-flight ceiling validation (65 C / 85 C) and that nothing is sent when the check cannot run, that stops are always sent, and the return shape. These are non-obvious behaviors an agent could not infer from structured fields.

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?

Front-loaded with the action and the hardware scope, then the start/stop split, then per-parameter notes. Well organized, though the START/STOP paragraph is dense and the ceiling-limit fact is repeated in both the prose and the temp_c note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter mutation tool with no annotations and no output schema, the description covers applicability, required-vs-optional inputs, validation rules, failure modes, and return value. Nothing an agent needs to invoke it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 13% (just duration_min), so the description must compensate, and it documents all eight parameters in prose — including the crucial numeric encoding of mode (1/0), the 0-based ams_id, per-unit temperature ceilings, and the humidity/rotate_tray hints. The two optional flags (humidity, rotate_tray) are described only vaguely ('Optional target humidity', 'Optional tray-rotation flag'), leaving their valid ranges and effects unstated.

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?

States a specific verb pair (start/stop) and a specific resource (AMS 2 Pro / AMS HT active dry cycle), scoped to Bambu printers that own one of those units. This separates it cleanly from advisory siblings like drying_advisor and from status readers like ams_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use branching: mode=1 start requires temp_c, duration_min > 0, and cooling_temp_c >= 45; mode=0 stop needs only ams_id. It also states when the tool is not applicable ('other printers and plain AMS / AMS Lite units return an error'), which is exactly the exclusion guidance an agent needs.

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