Skip to main content
Glama

multi_color_copies

Prints multiple copies of the same 3D model, each in a different AMS color. Auto-detects loaded filament trays or lets you specify AMS slots and colors.

Instructions

Print multiple copies of the same model, each in a different AMS color.

Takes a single model file and produces a multi-color print where each
copy uses a different AMS filament slot.  Perfect for "print 4 lids
in 4 different colors" workflows.

**Auto-detect mode** (default): omit *copies*, *ams_slots*, and
*colors* — the tool queries the AMS, finds all loaded trays matching
*material*, and prints one copy per loaded tray.

**Manual mode**: specify *ams_slots* (and optionally *colors*) to
choose exactly which AMS trays to use and how many copies.

Requires PrusaSlicer or OrcaSlicer installed locally.  The printer
must be idle and have an AMS with loaded filament.

:param model_path: Path to the model file (STL or OBJ).
:param copies: Number of copies.  Auto-detected from AMS if omitted.
:param ams_slots: Explicit AMS slot indices (0-based) per copy.
    E.g. ``[0, 1, 2, 3]`` for all 4 AMS Lite trays.
:param colors: Hex color strings per copy for slicer preview.
    E.g. ``["#FF0000", "#00FF00", "#0000FF", "#FFFF00"]``.
    Auto-read from AMS if omitted.
:param material: Material type filter for AMS auto-detect
    (default ``"PLA"``).  Only trays matching this type are used.
:param spacing_mm: Gap between copies on the plate (default 10 mm).
:param printer_id: Printer model ID for slicer profile selection.
:param slicer_path: Explicit path to slicer binary.
:returns: Dict with print result, object details, and AMS mapping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorsNo
copiesNo
materialNoPLA
ams_slotsNo
model_pathYes
printer_idNo
spacing_mmNo
slicer_pathNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes auto-detect behavior (queries AMS, prints one per loaded tray) and prerequisites (idle printer, loaded AMS). It implies a destructive action (printing) but does not explicitly state that a print job will be started. Additional clarity on side effects would raise the score.

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?

The description is well-structured with clear sections, bullet points for modes, and a parameter list. Every sentence adds value, and there is no redundancy or verbose phrasing. It is appropriately sized for the tool's complexity.

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?

The description covers modes, prerequisites, and parameter usage. It mentions the return value (dict with print result, object details, AMS mapping). However, it does not address potential error cases (e.g., no AMS slots matching material, slicer not found) or provide examples of return values. Still, it is mostly complete for the tool's complexity.

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?

Although schema documentation coverage is 0%, the description provides detailed explanations for all 8 parameters, including usage context (e.g., auto-detect mode vs manual mode) and defaults. This far exceeds the baseline of 3 for a high-coverage schema and adds significant value beyond the schema's type/required fields.

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?

The description clearly states the tool's purpose: 'Print multiple copies of the same model, each in a different AMS color.' It uses specific verbs and resources, and the unique angle of multi-color copying via AMS slots distinguishes it from siblings like multi_copy_print or multi_material_print.

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

Usage Guidelines4/5

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

The description provides excellent guidance on when to use auto-detect vs manual modes, including which parameters to omit for auto-detect. It also lists prerequisites (PrusaSlicer/OrcaSlicer, idle printer, loaded AMS). However, it does not explicitly compare to sibling tools or state when not to use this tool in favor of 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