Skip to main content
Glama

slice_and_estimate

Slice a 3D model to get print time, filament usage, cost, printability analysis, and adhesion recommendations.

Instructions

Primary estimation tool — slice a 3D model and return time, filament, cost, and printability analysis.

        For G-code files (already sliced), use ``estimate_cost`` instead.
        For quick volume-based estimates without slicing, use ``estimate_material_cost``.

        Slices the model using PrusaSlicer or OrcaSlicer, parses the
        output G-code for time and filament metadata, runs printability
        analysis (for STL/OBJ/3MF inputs), and returns adhesion
        recommendations — all without uploading or starting a print.

        Use this tool to answer "how long will this take?" or "how much
        filament will I use?" before committing to a print job.

        Args:
            input_path: Path to the input file (STL, OBJ, 3MF, STEP, AMF).
            printer_id: Optional printer model ID for bundled profile
                auto-selection (e.g. ``"bambu_a1"``, ``"prusa_mini"``).
            profile: Path to a slicer profile/config file (.ini or .json).
                Takes precedence over ``printer_id`` auto-selection.
            material: Filament material for weight and adhesion estimates
                (e.g. ``"PLA"``, ``"PETG"``, ``"ABS"``).  Default is
                ``"PLA"``.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNo
materialNoPLA
input_pathYes
printer_idNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: slicing with PrusaSlicer or OrcaSlicer, parsing G-code, printability analysis, adhesion recommendations, and that it does not upload or start a print. However, it does not detail output format or error handling.

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 clear initial paragraph and bullet arguments. It is slightly verbose but every sentence adds value. Front-loaded with key differentiators.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and no output schema, the description covers core functionality but lacks detail on output format, error scenarios, or edge cases. It mentions return types but not structure.

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 description coverage is 0%, but the description adds extensive meaning: it explains supported file formats for input_path, printer_id with examples, profile precedence, and material with default and examples. This fully compensates for the lack of schema descriptions.

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 it is the primary estimation tool for slicing 3D models and returning time, filament, cost, and printability analysis. It differentiates itself from 'estimate_cost' and 'estimate_material_cost' by specifying input types and use cases.

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 explicitly tells when to use this tool (before committing to a print job) and when not to (for G-code files use 'estimate_cost', for quick volume estimates use 'estimate_material_cost'). It provides context for usage.

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