Skip to main content
Glama

retry_print_with_fix

Automatically diagnose a failed print, apply slicer fixes, validate the mesh, re-slice, and restart printing.

Instructions

Diagnose the last print failure and re-slice + print with fixes.

        When a print fails, call this tool instead of manually chaining
        ``diagnose_print_failure_live`` → ``slice_and_print``.  It:

        1. Reads live printer state and analyses the model geometry to
           diagnose the failure (unless ``skip_diagnosis`` is True).
        2. Auto-detects the loaded material from the AMS when
           ``material`` is omitted and the printer supports it.
        3. Merges diagnosis-recommended slicer overrides with any
           ``custom_overrides`` you supply (your overrides win on
           conflict).
        4. Re-validates the mesh's printability before re-slicing.  A
           retry path that re-sends a broken mesh is the highest-
           value place to validate — the previous attempt already
           failed, and slicer overrides can't fix mesh-level issues.
           Bypass with ``skip_validation=True`` if the caller already
           validated.
        5. Re-slices the (possibly auto-repaired) mesh with the merged
           overrides, uploads the result, and starts the print.

        Args:
            model_path: Path to the STL/OBJ/3MF that failed.
            printer_name: Target printer name.  Omit for the default
                printer.
            material: Filament material (e.g. ``"PLA"``, ``"ABS"``).
                Auto-detected from AMS when omitted.
            printer_id: Printer model ID for intelligence lookup
                (e.g. ``"bambu_a1"``).
            custom_overrides: JSON object of additional slicer overrides
                to merge on top of the diagnosis recommendations
                (e.g. ``'{"brim_width": "8"}'``).  Your values win on
                conflict.
            skip_diagnosis: If True, skip the failure diagnosis step and
                re-slice using only ``custom_overrides``.
            skip_validation: If True, bypass the pre-print mesh
                validation gate.  Defaults to False — designs are
                pre-tested for printability before the retry reaches
                the printer.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
materialNo
model_pathYes
printer_idNo
printer_nameNo
preview_tokenNo
skip_diagnosisNo
skip_validationNo
custom_overridesNo
Install Server

TDQS

A4.8/5.0
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 of behavioral disclosure. It details steps: reads live state, analyzes geometry, auto-detects material, merges overrides, re-validates mesh, repairs if needed, re-slices, uploads, and starts print. It even explains the rationale for validation and states custom overrides win on conflict, demonstrating thorough transparency.

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 verbose but well-structured with numbered steps and a clear Args section. While it is longer than necessary, every section adds value, and the key purpose is front-loaded. Some prose could be trimmed without loss, but overall it's organized.

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?

For a complex tool that initiates a print, the description covers the entire workflow, parameter semantics, bypass options, and even the rationale for mesh validation. It lacks output details but no output schema exists, and the tool's side effects (starting a print) are clear. The preview_token omission is minor but doesn't detract from overall completeness.

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

Parameters4/5

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

The description explains most parameters meaningfully: model_path, printer_name, material (with auto-detection), printer_id, custom_overrides (with JSON example), skip_diagnosis, and skip_validation (with default). However, it omits 'preview_token' entirely, leaving that parameter undocumented. Since schema coverage is 0%, this omission is a notable gap.

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: 'Diagnose the last print failure and re-slice + print with fixes.' It uses specific verbs and resource, and distinguishes from siblings by explicitly mentioning the manual chain of diagnose_print_failure_live → slice_and_print, clarifying it as the preferred retry path.

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?

The description provides explicit when-to-use guidance: 'When a print fails, call this tool instead of manually chaining diagnose_print_failure_live → slice_and_print.' It also explains when to skip diagnosis or validation via parameters, giving context for alternatives and bypass conditions.

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

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