Kiln

Overview Schema Source Related Servers Discussions Admin

estimate_print_cost_from_mesh

Read-only

Calculate total 3D print cost directly from mesh geometry, covering material, support, adhesion, and electricity without slicing or G-code.

Instructions

Estimate total print cost from a 3D model file.

        Calculates material, support, adhesion, and electricity costs directly
        from mesh geometry — no G-code or slicing required. Includes a detailed
        cost breakdown and actionable recommendations to reduce cost.

        Supported materials: pla, pla+, petg, abs, tpu, asa, nylon, pc,
        cf-pla, silk-pla, hips, pva, pp, peek.

        Args:
            file_path: Path to a mesh (.stl, .obj, .glb, .3mf) or a CAD
                file (.step, .stp), which is converted automatically.
            material: Material type (default "pla").
            infill_percent: Interior fill percentage 0-100 (default 20).
            wall_layers: Number of perimeter shells (default 3).
            layer_height_mm: Layer height in mm (default 0.2).
            nozzle_mm: Nozzle diameter in mm.  Leave unset for the only
                printer Kiln knows of, else 0.4; ``nozzle`` in the reply
                says which.
            include_supports: Estimate support material cost (default False).
            support_density: Support infill percentage (default 15).
            adhesion_type: Bed adhesion type: "none", "brim", or "raft".
            electricity_rate: Electricity cost in $/kWh (default 0.12).
            printer_wattage: Printer power consumption in watts (default 200).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "estimate_print_cost_from_mesh"
  }
}

Input Schema

Name	Required	Description
`material`	No	Material type (default "pla"). Default: "pla".
`file_path`	Yes	Path to a mesh (.stl, .obj, .glb, .3mf) or a CAD file (.step, .stp), which is converted automatically.
`nozzle_mm`	No	Nozzle diameter in mm. Leave unset for the only printer Kiln knows of, else 0.4; ``nozzle`` in the reply says which.
`wall_layers`	No	Number of perimeter shells (default 3). Default: 3.
`adhesion_type`	No	Bed adhesion type: "none", "brim", or "raft". Default: "none".
`infill_percent`	No	Interior fill percentage 0-100 (default 20). Default: 20.0.
`layer_height_mm`	No	Layer height in mm (default 0.2). Default: 0.2.
`printer_wattage`	No	Printer power consumption in watts (default 200). Default: 200.0.
`support_density`	No	Support infill percentage (default 15). Default: 15.0.
`electricity_rate`	No	Electricity cost in $/kWh (default 0.12). Default: 0.12.
`include_supports`	No	Estimate support material cost (default False). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.5.1Nov 5, 2026

changedInput schema / properties / adhesion_type / description

Previous value: -"Default: \"none\"."New value: +"Bed adhesion type: \"none\", \"brim\", or \"raft\". Default: \"none\"."

changedInput schema / properties / electricity_rate / description

Previous value: -"Default: 0.12."New value: +"Electricity cost in $/kWh (default 0.12). Default: 0.12."

addedInput schema / properties / file_path / description

Added value: +"Path to a mesh (.stl, .obj, .glb, .3mf) or a CAD file (.step, .stp), which is converted automatically."

changedInput schema / properties / include_supports / description

Previous value: -"Default: false."New value: +"Estimate support material cost (default False). Default: false."

changedInput schema / properties / infill_percent / description

Previous value: -"Default: 20.0."New value: +"Interior fill percentage 0-100 (default 20). Default: 20.0."

changedInput schema / properties / layer_height_mm / description

Previous value: -"Default: 0.2."New value: +"Layer height in mm (default 0.2). Default: 0.2."

changedInput schema / properties / material / description

Previous value: -"Default: \"pla\"."New value: +"Material type (default \"pla\"). Default: \"pla\"."

addedInput schema / properties / nozzle_mm / description

Added value: +"Nozzle diameter in mm.  Leave unset for the only printer Kiln knows of, else 0.4; ``nozzle`` in the reply says which."

changedInput schema / properties / printer_wattage / description

Previous value: -"Default: 200.0."New value: +"Printer power consumption in watts (default 200). Default: 200.0."

changedInput schema / properties / support_density / description

Previous value: -"Default: 15.0."New value: +"Support infill percentage (default 15). Default: 15.0."

changedInput schema / properties / wall_layers / description

Previous value: -"Default: 3."New value: +"Number of perimeter shells (default 3). Default: 3."

Changed21 schema fields changedv1.5.0Oct 23, 2026
- removedInput schema / properties / adhesion_type / default
```
Removed value: -"none"
```
- addedInput schema / properties / adhesion_type / description
```
Added value: +"Default: \"none\"."
```
- removedInput schema / properties / electricity_rate / default
```
Removed value: -0.12
```
- addedInput schema / properties / electricity_rate / description
```
Added value: +"Default: 0.12."
```
- removedInput schema / properties / include_supports / default
```
Removed value: -false
```
- addedInput schema / properties / include_supports / description
```
Added value: +"Default: false."
```
- removedInput schema / properties / infill_percent / default
```
Removed value: -20
```
- addedInput schema / properties / infill_percent / description
```
Added value: +"Default: 20.0."
```
- removedInput schema / properties / layer_height_mm / default
```
Removed value: -0.2
```
- addedInput schema / properties / layer_height_mm / description
```
Added value: +"Default: 0.2."
```
- removedInput schema / properties / material / default
```
Removed value: -"pla"
```
- addedInput schema / properties / material / description
```
Added value: +"Default: \"pla\"."
```
- addedInput schema / properties / nozzle_mm / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / nozzle_mm / default
```
Removed value: -0.4
```
- removedInput schema / properties / nozzle_mm / type
```
Removed value: -"number"
```
- removedInput schema / properties / printer_wattage / default
```
Removed value: -200
```
- addedInput schema / properties / printer_wattage / description
```
Added value: +"Default: 200.0."
```
- removedInput schema / properties / support_density / default
```
Removed value: -15
```
- addedInput schema / properties / support_density / description
```
Added value: +"Default: 15.0."
```
- removedInput schema / properties / wall_layers / default
```
Removed value: -3
```
- addedInput schema / properties / wall_layers / description
```
Added value: +"Default: 3."
```
First observedv0.1.0Jul 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them: it discloses what the response contains (itemized material/support/adhesion/electricity breakdown plus cost-reduction recommendations) and explains the fallback behavior for nozzle_mm via the ``nozzle`` key in the reply.

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

Conciseness3/5

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

The lead paragraph is well front-loaded and informative, but the Args block duplicates the input schema nearly verbatim, including repeated default annotations ('default 20' followed by 'Default: 20.0'). The result reads as a docstring rather than a description, with meaningful padding in the parameter list.

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?

For an 11-parameter estimation tool with no output schema, the description supplies the missing return-shape information (cost breakdown categories, recommendations, nozzle key) and file-format support. It lacks only a statement of whether the estimate is deterministic, what units the total is in, or how expensive the computation is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 11 parameters, and the Args block largely restates it. The only added nuance is the enumeration of supported material strings and the note about leaving nozzle_mm unset for the sole known printer, which is marginal over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Estimate total print cost from a 3D model file') and adds the key differentiator that costs are computed directly from mesh geometry with no G-code or slicing. That implicitly separates it from the many slicing- and cost-related siblings (slice_and_estimate, estimate_material_cost, estimate_print_time), though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'no G-code or slicing required' line gives an implied usage boundary and the mesh/CAD file support is stated, but there is no explicit when-to-use guidance, no exclusion telling the agent to prefer a different estimator when a sliced file already exists, and no mention of prerequisites or cost.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server