Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

estimate_print_progress

Estimate print completion time by splitting the job into phases and using historical outcome data. Reads live printer status when elapsed time or layer numbers are omitted.

Instructions

Estimate print progress with phase-aware time prediction.

        Breaks a print into phases -- preparing, printing, cooling, and
        post-processing -- and uses historical data from the print outcomes
        database to estimate time remaining.  Typically more accurate than
        raw firmware estimates for predicting true completion time.

        Supply ``elapsed_seconds``, ``total_layers``, and ``current_layer``
        when available; any omitted values will be read from the printer's
        live status.

        :param printer_name: Printer running the job.
        :param elapsed_seconds: Seconds elapsed since print start.  Omit to
            read from printer status.
        :param total_layers: Total layer count for the job.  Omit to read
            from printer/G-code metadata.
        :param current_layer: Current layer being printed.  Omit to read
            from printer status.

        See also: ``printer_status()``, ``get_print_outcomes()``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printer_nameYes
total_layersNo
current_layerNo
elapsed_secondsNo
Install Server

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description must disclose behavior. It describes data sources (printer status, print outcomes database) and phases. While it implies read-only, it does not explicitly state non-destructiveness, but the verb and context are clear enough.

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?

Well-structured with a summary sentence, then details, parameter list, and references. A bit lengthy but every sentence contributes; front-loads the core purpose.

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?

Covers methodology, parameter usage, and relative accuracy. Lacks description of the return value format, but for an estimation tool, the output is typically intuitive. No output schema exists, so some expectation of return details is reasonable but not critical.

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?

Schema coverage is 0%, yet the description adds full meaning: explains printer_name, and for each optional parameter, clarifies 'Omit to read from printer status' and context (e.g., 'Seconds elapsed since print start'). This compensates for the schema's lack of description.

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 'Estimate print progress with phase-aware time prediction', specifying the verb and resource. It distinguishes from sibling tools like estimate_print_time by highlighting phase-awareness and historical data usage.

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?

Explicit guidance: 'Typically more accurate than raw firmware estimates' and instructions to supply parameters or omit for live readings. The 'See also' section directs to related tools (printer_status, get_print_outcomes), aiding decision-making.

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