Skip to main content
Glama

slice_and_print

Slice a 3D model, upload it, and start printing in one step with automatic bed adhesion analysis and pre-print validation.

Instructions

Slice a 3D model (STL/3MF) + upload + print in one step (basic pipeline).

        For a more comprehensive pipeline with validation and profile auto-detection,
        use ``run_quick_print``. For custom slicer overrides, use ``run_reslice_and_print``.
        Automatically analyzes bed adhesion and adds brim/raft when needed
        based on model geometry, material warp tendency, and printer type.
        This adhesion intelligence only activates when no custom profile is
        supplied.

        Pre-print validation gate: mesh inputs (.stl/.obj/.3mf/.step/.glb)
        run through Kiln's full validation pipeline before slicing —
        format check, watertight check, auto-repair, printability scoring
        (0-100), bed-fit, and material checks.  Designs that fail the gate
        are blocked before reaching the printer; auto-repaired meshes are
        sliced from the repaired path.  Pass ``skip_validation=True`` to
        bypass (e.g. for already-validated meshes or pre-sliced 3MFs).

        Args:
            input_path: Path to the 3D model file (STL, 3MF, STEP, etc.).
            printer_name: Target printer name.  Omit for the default printer.
            profile: Path to a slicer profile/config file.
            printer_id: Optional printer model ID for bundled profile
                auto-selection (e.g. ``"prusa_mini"``).
            material: Filament material (e.g. ``"PLA"``, ``"ABS"``).  Affects
                automatic brim/raft decisions.
            metadata: Optional dict of pass-through fields.  When
                kiln-pro (https://kiln3d.com) is installed it
                consumes keys here to generate a printable
                assembly manual alongside the print, surfacing it
                under ``response["assembly_manual"]``.  Without
                kiln-pro the metadata is silently ignored.
                Recognised keys (all optional):
                ``assembly_json``, ``manual_output_dir``,
                ``manual_design_name``, ``manual_branding``,
                ``manual_co_brand_name``, ``manual_languages``,
                ``manual_cover_language``.  Multi-language and
                co-brand are kiln-pro Business+ features
                (https://kiln3d.com/pricing).
            skip_validation: Bypass the pre-print validation gate.
                Defaults to False — designs are pre-tested for
                printability before they reach the printer.  Set to
                True only when the caller has already validated the
                mesh (e.g. ``validate_and_prepare`` was just called)
                or when the input is a pre-sliced 3MF the validator
                can't introspect.

        Combines ``slice_model``, ``upload_file``, and ``start_print`` into
        a single action.

        Branch on ``print_start`` — one field, three values, and the
        nested ``print`` block carries the identical pair so the two
        halves cannot disagree:

        - ``"started"``: the printer, asked after the command, is printing.
        - ``"accepted"``: the command was sent and not refused, and the
          machine has not confirmed it is running.  Normal during the
          start-up transient (homing, AMS load, calibration).  Call
          ``printer_status()`` to watch it start.
        - ``"failed"``: the printer, asked after the command, is idle or
          errored — it did not take the job.

        ``success`` is ``False`` only for ``"failed"``.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNo
materialNo
metadataNo
input_pathYes
printer_idNo
auto_centerNo
printer_nameNo
preview_tokenNo
skip_validationNo
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior. It details the combined actions, the automatic brim/raft behavior, the validation gate and skip_validation, and the print_start outcome values ('started', 'accepted', 'failed') with their meanings and when success is false. This is comprehensive and transparent.

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 lengthy but well-structured with clear sections (overview, alternatives, adhesion, validation, parameters, print_start branching). While detailed, it avoids redundancy and each part serves a purpose. It is appropriately sized for a tool combining three actions.

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?

The description provides extensive context, including behavior, parameter semantics, and return outcomes via print_start and success. It lacks explanations for auto_center and preview_token, and there is no output schema, but the description compensates well for most aspects. It feels nearly complete but not fully exhaustive.

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: input_path, printer_name, profile, printer_id, material, metadata (including recognized keys), and skip_validation. However, it omits explanations for auto_center and preview_token, leaving these parameters undefined in the text. Coverage is strong but not complete.

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 function: 'Slice a 3D model (STL/3MF) + upload + print in one step' and explicitly mentions it combines slice_model, upload_file, and start_print. It also differentiates from siblings by recommending run_quick_print for comprehensive pipelines and run_reslice_and_print for custom overrides.

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 guidance on when to use alternatives: 'For a more comprehensive pipeline... use run_quick_print. For custom slicer overrides, use run_reslice_and_print.' It also explains conditions for adhesion analysis and validation bypass, giving clear usage context.

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