Skip to main content
Glama

reprint_with_material

Reprint a 3D model in a different material by automatically adjusting slicer settings like temperature and speed. Simply provide the file and target material to start printing.

Instructions

Reprint a model with a different material — auto-adjusts temperatures, speeds, and retraction for the new material.

One-shot convenience tool: looks up the target material's optimal slicer
settings, merges any extra overrides you provide, reslices the model,
runs a safety check, uploads to the printer, and starts the print.

Use this when you want to reprint an existing model in a different
material (e.g. PLA → PETG for outdoor durability, or PLA → TPU for
flexibility). The tool handles all the slicer parameter changes
automatically.

Example: "Reprint my grip extension in PETG instead of PLA"::

    reprint_with_material(
        file_path="/path/to/grip_extension.stl",
        material_id="petg",
        printer_name="my_bambu",
        printer_id="bambu_a1",
        use_ams=True,
        ams_mapping="[1]",  # PETG is in AMS slot 1
    )

Requires PrusaSlicer or OrcaSlicer installed locally.

Args:
    file_path: Path to the model file (STL, 3MF, STEP, OBJ).
    material_id: Target material (e.g. ``"petg"``, ``"tpu"``).
    printer_name: Registered printer name in fleet. If omitted,
        uses the default printer.
    printer_id: Printer model ID for profile selection
        (e.g. ``"bambu_a1"``, ``"ender3"``).
    extra_overrides: Optional JSON string of additional slicer
        overrides to merge on top of the material defaults
        (e.g. ``'{"fill_density": "30%"}'``).
    use_ams: Enable AMS filament feeding (Bambu printers).
    ams_mapping: JSON string of AMS slot indices (e.g. ``"[1]"``).
        Maps each extruder/filament to an AMS tray position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
use_amsNo
file_pathYes
printer_idNo
ams_mappingNo
material_idYes
printer_nameNo
extra_overridesNo
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It explains the entire workflow: looks up settings, merges overrides, reslices, runs a safety check, uploads, and starts the print. It also discloses the local slicer requirement and side effects (starts a print).

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 with a one-liner, process summary, usage guidance, example, requirement note, and argument list. It is longer than strictly necessary but each section adds value. The example helps understanding.

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?

Considering the tool's complexity (7 parameters, no output schema), the description provides sufficient information for an agent to invoke it correctly. It covers the workflow, parameter semantics, and prerequisites. Minor missing details: error handling if slicer is not installed or material not found.

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 the context signals indicate 0% schema coverage, the description itself documents all 7 parameters with clear explanations and even provides JSON examples for extra_overrides and ams_mapping. This adds significant value beyond the bare 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 core action: 'Reprint a model with a different material — auto-adjusts temperatures, speeds, and retraction for the new material.' It distinguishes itself from siblings by specifying it's a one-shot convenience tool for material changes, unlike general reslicing or printing tools.

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 explains when to use the tool (e.g., reprint in a different material like PLA→PETG) and provides an example. It also mentions a requirement (PrusaSlicer or OrcaSlicer installed locally). However, it does not explicitly state when not to use it or suggest 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