Skip to main content
Glama

complete_print_recovery

Finalize a print recovery session by recording success or failure. When recovery fails and alternative printers are provided, the response includes a reroute recommendation based on progress and printer status.

Instructions

Mark a recovery session as completed.

        On failure (success=False) AND when ``alternative_printers``
        is supplied AND kiln-pro is installed, the response carries
        a ``reroute_recommendation`` block — the rerouter's seven-rule
        verdict on whether the failed job should move to one of the
        alternatives.  Recommendation only; the agent must run the
        actual reroute via ``submit_job`` / ``start_print``.

        Args:
            session_id: The session_id to complete.
            success: Whether the recovery was ultimately successful.
            notes: Final notes about the recovery outcome.
            alternative_printers: Optional fleet of alternative
                printer dicts (each with ``printer_id`` plus optional
                ``is_idle``, ``supported_materials``,
                ``build_volume_mm``, ``success_rate``).  When
                supplied alongside ``success=False``, the response
                will include a ``reroute_recommendation`` from the
                pro rerouter (patent KILN-003 claim 5).  Single-printer
                setups can omit this.
            completion_pct_at_failure: How far the failed print got
                (0.0–1.0).  Below 10% the rerouter prefers
                same-device restart over reroute.  Defaults to 0
                (treated as low progress).
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
successYes
session_idYes
alternative_printersNo
completion_pct_at_failureNo
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: the conditional inclusion of a 'reroute_recommendation' in the response, the impact of 'completion_pct_at_failure' on rerouter logic, and the fact that the recommendation is advisory only. No contradictions.

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 summary sentence, a condition block, and a parameter list. It is front-loaded with the main action. Minor detail like 'patent KILN-003 claim 5' is slightly tangential but does not detract significantly.

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 the tool's complexity (5 params, no output schema, no annotations), the description covers behavior, parameter semantics, and the conditional response. It also tells the agent what to do next. It could mention the default response on success, but the provided information is sufficient for most use cases.

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 schema has 0% description coverage, so the description carries full burden. It provides detailed explanations for all 5 parameters, including structure for 'alternative_printers' and behavioral context for 'completion_pct_at_failure' (threshold effect). 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 starts with 'Mark a recovery session as completed,' which is a specific verb+resource. It clearly distinguishes this tool from sibling recovery tools like 'plan_print_recovery' and 'start_print_recovery' by focusing on completion and the optional reroute recommendation.

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 clearly states when to use the tool (to complete a recovery session) and provides guidance on when the reroute recommendation appears (on failure with alternative printers and kiln-pro installed). It also instructs the agent to call other tools for actual reroute. However, it does not explicitly exclude usage in other scenarios.

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