Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

compare_print_options

Read-only

Compare local 3D printing costs with outsourced manufacturing quotes to help agents recommend the lower-cost production option.

Instructions

Compare local printing cost vs. outsourced manufacturing.

Runs a local cost estimate and (if Craftcloud is configured) fetches
a fulfillment quote, then returns a side-by-side comparison to help
agents recommend the best option.

Args:
    file_path: Path to the G-code file (for local) or model file
        (STL/3MF for fulfillment).  If a G-code file is provided,
        only local estimate is returned.
    material: Filament material for the local estimate (PLA, PETG, …).
        Leave empty to use what the file was sliced for, PLA when it
        names nothing.  When Kiln's servers answer, the
        local estimate also carries a ``cost_intelligence`` field; what
        it holds depends on the tier.
    fulfillment_material_id: Material ID from ``fulfillment_materials``
        for the outsourced quote.  If omitted, the fulfillment quote
        is skipped.
    quantity: Number of copies for fulfillment (default 1).
    electricity_rate: Cost per kWh in USD (default 0.12).
    printer_wattage: Printer power consumption in watts (default 200).
    shipping_country: ISO country code for fulfillment shipping.
    printer_id: Optional registered printer the local print is for;
        passed on with the file when kiln-pro is asked.

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": "compare_print_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoFilament material for the local estimate (PLA, PETG, …). Leave empty to use what the file was sliced for, PLA when it names nothing. When Kiln's servers answer, the local estimate also carries a ``cost_intelligence`` field; what it holds depends on the tier. Default: "".
quantityNoNumber of copies for fulfillment (default 1). Default: 1.
file_pathYesPath to the G-code file (for local) or model file (STL/3MF for fulfillment). If a G-code file is provided, only local estimate is returned.
printer_idNoOptional registered printer the local print is for; passed on with the file when kiln-pro is asked. Default: "".
printer_wattageNoPrinter power consumption in watts (default 200). Default: 200.0.
electricity_rateNoCost per kWh in USD (default 0.12). Default: 0.12.
shipping_countryNoISO country code for fulfillment shipping. Default: "US".
fulfillment_material_idNoMaterial ID from ``fulfillment_materials`` for the outsourced quote. If omitted, the fulfillment quote is skipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • changedInput schema / properties / electricity_rate / description
      Previous value: -"Default: 0.12."New value: +"Cost per kWh in USD (default 0.12). Default: 0.12."
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the G-code file (for local) or model file (STL/3MF for fulfillment).  If a G-code file is provided, only local estimate is returned."
    • addedInput schema / properties / fulfillment_material_id / description
      Added value: +"Material ID from ``fulfillment_materials`` for the outsourced quote.  If omitted, the fulfillment quote is skipped."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Filament material for the local estimate (PLA, PETG, …). Leave empty to use what the file was sliced for, PLA when it names nothing.  When Kiln's servers answer, the local estimate also carries a ``cost_intelligence`` field; what it holds depends on the tier. Default: \"\"."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"Optional registered printer the local print is for; passed on with the file when kiln-pro is asked. Default: \"\"."
    • 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 / quantity / description
      Previous value: -"Default: 1."New value: +"Number of copies for fulfillment (default 1). Default: 1."
    • changedInput schema / properties / shipping_country / description
      Previous value: -"Default: \"US\"."New value: +"ISO country code for fulfillment shipping. Default: \"US\"."
  2. Changed12 schema fields changedv1.5.0
    • removedInput schema / properties / electricity_rate / default
      Removed value: -0.12
    • addedInput schema / properties / electricity_rate / description
      Added value: +"Default: 0.12."
    • removedInput schema / properties / fulfillment_material_id / default
      Removed value: -null
    • removedInput schema / properties / material / default
      Removed value: -"PLA"
    • addedInput schema / properties / material / description
      Added value: +"Default: \"\"."
    • addedInput schema / properties / printer_id
      Added value: +{
+  "description": "Default: \"\".",
+  "title": "Printer Id",
+  "type": "string"
+}
    • removedInput schema / properties / printer_wattage / default
      Removed value: -200
    • addedInput schema / properties / printer_wattage / description
      Added value: +"Default: 200.0."
    • removedInput schema / properties / quantity / default
      Removed value: -1
    • addedInput schema / properties / quantity / description
      Added value: +"Default: 1."
    • removedInput schema / properties / shipping_country / default
      Removed value: -"US"
    • addedInput schema / properties / shipping_country / description
      Added value: +"Default: \"US\"."
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, the description discloses that fulfillment requires Craftcloud to be configured, that G-code input degrades to local-only, and that a tier-dependent cost_intelligence field may appear. It does not describe failure behavior or the shape of the comparison result, which matters since no output schema exists.

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 summary is well front-loaded and earns its place, but the long Args section duplicates the schema field-for-field, including defaults and type hints the agent already receives. That is redundant bulk rather than added meaning.

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 8-parameter, read-only comparison tool with no output schema, the description covers the input branching and the optional fulfillment path adequately. A short note on what the returned comparison contains (cost fields, savings delta) would close the remaining gap.

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 already 100%, and the Args block largely restates the same parameter text verbatim. The added value is minimal — only the fallback semantics for material are reinforced, not extended.

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 opening line states a specific verb and resource — 'compare local printing cost vs. outsourced manufacturing' — and the second sentence explains the two-step mechanism (local estimate + optional fulfillment quote). This clearly separates it from siblings such as estimate_cost, fulfillment_quote, and print_cost_intelligence.

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

Usage Guidelines4/5

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

It gives concrete conditional guidance: a G-code file yields only the local estimate, and omitting fulfillment_material_id skips the outsourced quote. It does not explicitly name alternative tools (e.g., 'use estimate_cost for local only'), so it stops short of full when/when-not routing.

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

Deploy Server

Other Tools