Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

print_cost_intelligence

Read-only

Calculate what filament changes add to a 3D print's cost, identify ways to cut that cost, and compare the total with a reprint priced in.

Instructions

What a print's filament changes cost and how to cut them, and the cost with a reprint priced in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "print_cost_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
filamentsNoPublic Kiln's per-filament entries for the same file (``tool``, ``material``, ``weight_g``, ``length_m``, ``cost_usd``), so the breakdown is priced exactly as the total was.
file_nameNoThe file's name, for the answer. Default: "".
file_pathNoA local ``.gcode`` or sliced ``.3mf`` instead. Default: "".
printer_idNoThe printer the print is for. Default: "".
gcode_gz_b64NoThe G-code, gzip-compressed then base64 (what a served caller sends). Default: "".
total_cost_usdNoThe estimate's total, for the risk-adjusted figure. Default: 0.0.
estimated_time_secondsNoThe estimate's time, likewise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.1
    • addedInput schema / properties / estimated_time_seconds / description
      Added value: +"The estimate's time, likewise."
    • addedInput schema / properties / filaments / description
      Added value: +"Public Kiln's per-filament entries for the same file (``tool``, ``material``, ``weight_g``, ``length_m``, ``cost_usd``), so the breakdown is priced exactly as the total was."
    • changedInput schema / properties / file_name / description
      Previous value: -"Default: \"\"."New value: +"The file's name, for the answer. Default: \"\"."
    • changedInput schema / properties / file_path / description
      Previous value: -"Default: \"\"."New value: +"A local ``.gcode`` or sliced ``.3mf`` instead. Default: \"\"."
    • changedInput schema / properties / gcode_gz_b64 / description
      Previous value: -"Default: \"\"."New value: +"The G-code, gzip-compressed then base64 (what a served caller sends). Default: \"\"."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"The printer the print is for. Default: \"\"."
    • changedInput schema / properties / total_cost_usd / description
      Previous value: -"Default: 0.0."New value: +"The estimate's total, for the risk-adjusted figure. Default: 0.0."
  2. Addedv1.5.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that a reprint is priced into the figure and that cost-reduction advice is returned, which is useful output context, but it does not disclose the critical input behavior — that a caller must supply one of filaments, file_path, or gcode_gz_b64 for anything to be priced.

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?

It is a single short sentence with no filler, but the grammar is broken and back-loaded with an awkward clause ('a reprint priced in'), so it does not read cleanly or front-load the core purpose. Brevity is achieved at the cost of parseability.

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?

For a read-only analysis tool with seven all-optional parameters and no output schema, the description omits the one thing an agent most needs: the mutually alternative input modes (per-filament breakdown array vs. a local file path vs. base64 G-code). Given the complexity of those alternatives, the definition is only minimally complete.

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 each parameter (filaments entries, file_name, file_path, printer_id, gcode_gz_b64, total_cost_usd, estimated_time_seconds) is already documented. The description adds no syntax, format, or precedence detail beyond what the schema provides, so the baseline of 3 applies.

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

Purpose3/5

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

The description gestures at a specific scope — the cost impact of filament changes, ways to cut that cost, and a reprint-risk-adjusted figure — which distinguishes it somewhat from a plain cost estimate. But it is written as a fragment ("What a print's filament changes cost and how to cut them") with no clear verb or object, so an agent must infer that the tool analyzes and explains cost rather than computing a raw estimate.

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

Usage Guidelines2/5

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

There is no guidance on when to call this instead of the many cost siblings such as estimate_cost, estimate_material_cost, estimate_print_cost_from_mesh, or slice_and_estimate, nor any statement of prerequisites. The description only implies usage through its topic, leaving the routing decision to inference.

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