Skip to main content
Glama

estimate_print_time

Estimate print time and filament usage for 3D models by slicing STL/3MF/OBJ files or parsing existing G-code. Provides layer count and cost estimates directly.

Instructions

Estimate print time and filament usage for a model.

        Slices the model and parses the G-code for print time, filament
        length/weight, layer count, and cost estimates.

        For **already-sliced** G-code files, pass the ``.gcode`` path
        directly — it will be parsed without re-slicing.

        **See also:** ``slice_and_estimate`` for a fuller analysis that
        includes printability scoring and adhesion recommendations.

        :param file_path: Path to STL/3MF/OBJ or .gcode file.
        :param profile: Optional slicer profile path.
        :param printer_id: Optional printer model ID for bundled profile
            (e.g. ``"bambu_a1"``).  Used when no explicit profile is given.
        :param slicer_path: Optional explicit slicer binary path.
        :returns: Dict with time, filament, and layer estimates.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNo
file_pathYes
printer_idNo
slicer_pathNo
Behavior4/5

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

Describes process: slices model and parses G-code for estimates. For .gcode files, it parses without re-slicing. Does not mention side effects, but 'estimate' implies read-only. Adequate given no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then parameter descriptions, then see also. Each sentence adds value. No fluff. Concise yet comprehensive.

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?

Explains parameters and behavior well. Lacks output schema, but description provides high-level return type ('Dict with time, filament, and layer estimates'). Sufficient for basic completeness, but could detail return keys.

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%, but description documents all four parameters: file_path, profile, printer_id, slicer_path, with clear usage notes (e.g., 'for bundled profile, e.g. bambu_a1'). Adds significant meaning beyond 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?

Description clearly states it estimates print time and filament usage. It specifies the verb 'estimate' and resources 'print time and filament usage'. It distinguishes from sibling 'slice_and_estimate' by contrasting scope.

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?

Explicitly states when to use: pass .gcode path for already-sliced files without reslicing. Provides alternative: see slice_and_estimate for fuller analysis. Clear 'when to use vs. 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