Skip to main content
Glama

get_active_material

Reads live tray data from Bambu Lab AMS hardware to return the active filament's type, color, remaining percentage, and temperature range. Returns 'unknown' for non-AMS printers.

Instructions

Get the filament physically active in the AMS hardware right now (Bambu Lab).

        Reads live tray data from the AMS hardware. For the software-tracked
        material (what was told to Kiln via ``set_material``), use
        ``get_material`` instead.

        For Bambu Lab printers with an AMS, reads the active tray and
        returns its type, colour, remaining percentage, and temperature
        range.  For non-Bambu printers (or printers without AMS), the
        material is reported as ``"unknown"``.

        ``tray_now == "255"`` normally means external spool.  On some
        A1/AMS Lite reports it can also mean the active slot was not
        reported even though AMS trays are present; in that case Kiln
        falls back to selected/target tray metadata or returns the
        loaded AMS candidates instead of claiming external spool.

        Args:
            printer_name: Named printer to query.  Omit to use the
                default printer.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printer_nameNo
Behavior5/5

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

Describes reading live tray data, return fields (type, colour, remaining %, temperature range), and fallback logic for ambiguous tray_now. No annotation provided, but description carries full burden and is thorough.

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?

Well-structured with clear paragraphs: purpose, differentiation, return details, edge case. Each sentence adds value without redundancy.

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?

Covers all necessary aspects: input, output, edge cases, fallback behavior. Adequate for a simple getter with one optional parameter and no output schema.

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

Parameters5/5

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

Docstring explains the single parameter 'printer_name' is optional and defaults to default printer. Schema only provides default null, so description adds meaningful guidance.

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?

Clearly states it 'Get the filament physically active in the AMS hardware right now' for Bambu Lab printers. Differentiates from sibling 'get_material' which tracks software-set material. Specific verb+resource with scope.

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?

Explicitly says to use 'get_material' for software-tracked material, and describes behavior for non-Bambu printers and edge case with tray_now==255. Provides clear when-to-use and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server