Skip to main content
Glama

multi_copy_print

Print multiple copies of a model on one build plate. Automatically arranges them in a grid with spacing, slices, and prints as a single job.

Instructions

Print multiple copies of a model arranged on one build plate.

Automatically arranges copies in a grid with spacing so they don't
overlap, slices the plate as a single job, and prints.

Uses PrusaSlicer's ``--duplicate`` flag when available (handles placement,
collision avoidance, and travel optimization). Falls back to STL mesh
duplication for OrcaSlicer or when fine control is needed.

Requires a slicer (PrusaSlicer or OrcaSlicer) installed locally.
The printer must be idle and connected.

Args:
    model_path: Path to input model (STL, OBJ).
    copies: Number of copies to print (2-20).
    printer_name: Registered printer name in fleet.
    printer_id: Printer model ID for auto-profile selection.
    spacing_mm: Gap between copies in mm (default 10).
    overrides: JSON string of slicer parameter overrides.
    slicer_path: Explicit path to the slicer binary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copiesYes
overridesNo
model_pathYes
printer_idNo
spacing_mmNo
slicer_pathNo
printer_nameNo
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. It details key behaviors: automatic grid arrangement, slicer selection (PrusaSlicer with --duplicate flag, fallback to OrcaSlicer), and prerequisites. It does not cover failure modes or side effects (e.g., file creation), but covers core behavior well.

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?

The description is well-structured: a concise opening sentence, followed by behavioral details, then a labeled parameter list. It is slightly longer than necessary but every sentence adds value. A bulleted or more compact format could improve scannability.

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?

Given no output schema and no annotations, the description adequately covers inputs, process, and prerequisites. It lacks explicit mention of return value (e.g., job ID or success status) and error handling, but for a print action tool, the core flow is sufficiently described.

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?

The input schema has 0% description coverage, so the description fully compensates by explaining each parameter's purpose, including format (e.g., STL, OBJ), range (copies 2-20), default (spacing 10mm), and nullable fields. This adds significant value beyond the raw schema.

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: printing multiple copies of a model on one build plate with automatic arrangement. It distinguishes itself by detailing the slicer-specific behavior and fallback mechanism, making it distinct from siblings like 'multi_color_copies' or 'arrange_parts_on_plate'.

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 clear usage context: when multiple copies are needed, with prerequisites (slicer installed, printer idle and connected). However, it does not explicitly mention when not to use this tool or list alternative tools for similar tasks, though the specificity of the tool makes this less critical.

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