Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

unload_filament

Pull filament out of the hotend — back into the AMS on Bambu, a heated retract elsewhere.

Instructions

Pull filament out of the hotend — back into the AMS on Bambu, a heated retract elsewhere.

Same temperature gate, verification, ``outcome`` vocabulary and wait
bound as ``load_filament``: on Bambu ``extrusion_verified`` is ``True``
once the AMS reports no tray feeding the nozzle (``tray_now`` 255); on
Klipper an ``UNLOAD_FILAMENT`` / ``M702`` macro is used when the config
has one; otherwise the hotend is heated and ``length_mm`` is retracted
(default 80).

Args:
    material / temperature / length_mm / wait_seconds / keep_hot /
        printer_name: as ``load_filament``.  Unload never retracts at
        the end (the filament is already out) but still turns the
        heater off unless ``keep_hot`` asks otherwise.

Input Schema

NameRequiredDescriptionDefault
keep_hotNoDefault: false.
materialNo
length_mmNo
temperatureNo
printer_nameNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4/5.0
Behavior4/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 well: it names the temperature gate, the wait bound, the platform-specific verification signal (extrusion_verified when tray_now is 255 on Bambu, UNLOAD_FILAMENT/M702 on Klipper), the fallback heated retract with default length_mm 80, and the side effect that the heater is switched off unless keep_hot is set. It stops short of describing failure modes or what happens if the filament is already absent.

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?

Front-loaded with the core action, then platform branches, then argument deltas — no filler sentence. The Args block is compressed and the one clarification that differs from load_filament (no end-of-cycle retract, heater still off) is called out explicitly.

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 six-parameter, zero-annotation, no-output-schema hardware tool this is solid: procedure, platform variance, verification signal and side effects are all covered. The remaining hole is that the return shape is only gestured at via 'outcome vocabulary' inherited from load_filament, and half the argument meanings live in another tool's text.

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 only 17%, so the description must compensate, and it enumerates all six parameters while giving real meaning only for length_mm (default 80), keep_hot (heater stays on) and temperature (the shared gate). The rest are deferred wholesale to 'as load_filament', which an agent without that sibling's description loaded cannot resolve.

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 and resource ('Pull filament out of the hotend') plus an explicit distinction from the AMS-back-into-tray Bambu behaviour and the heated-retract path elsewhere. An agent can tell this apart from load_filament or purge_filament without opening a schema.

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 operation is self-evident from the name and first line, and the description tells the agent that parameter semantics mirror load_filament. However, it never states when to prefer this over purge_filament or load_filament, nor any precondition such as the printer being idle or the hotend needing to be at temperature before calling.

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