Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

estimate_price

Read-only

Get a low-to-high price range for 3D-printed parts by specifying technology, volume or dimensions, and quantity before requesting a full quote.

Instructions

Get an instant price estimate before requesting a full quote.

        Args:
            technology: Manufacturing technology: FDM, SLA, SLS, MJF, or DMLS.
            volume_cm3: Part volume in cubic centimeters (if known).
            dimensions_x_mm: Bounding box X dimension in mm (alternative to volume).
            dimensions_y_mm: Bounding box Y dimension in mm.
            dimensions_z_mm: Bounding box Z dimension in mm.
            quantity: Number of copies (default 1).

        Returns a low/high price range based on typical per-cm3 pricing for
        the technology.  For exact pricing, use ``fulfillment_quote`` with a
        real model file.

        Either ``volume_cm3`` or all three dimension parameters must be provided.

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": {
      "technology": "<technology>"
    },
    "name": "estimate_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoNumber of copies (default 1). Default: 1.
technologyYesManufacturing technology: FDM, SLA, SLS, MJF, or DMLS.
volume_cm3NoPart volume in cubic centimeters (if known).
dimensions_x_mmNoBounding box X dimension in mm (alternative to volume).
dimensions_y_mmNoBounding box Y dimension in mm.
dimensions_z_mmNoBounding box Z dimension in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • addedInput schema / properties / dimensions_x_mm / description
      Added value: +"Bounding box X dimension in mm (alternative to volume)."
    • addedInput schema / properties / dimensions_y_mm / description
      Added value: +"Bounding box Y dimension in mm."
    • addedInput schema / properties / dimensions_z_mm / description
      Added value: +"Bounding box Z dimension in mm."
    • changedInput schema / properties / quantity / description
      Previous value: -"Default: 1."New value: +"Number of copies (default 1). Default: 1."
    • addedInput schema / properties / technology / description
      Added value: +"Manufacturing technology: FDM, SLA, SLS, MJF, or DMLS."
    • addedInput schema / properties / volume_cm3 / description
      Added value: +"Part volume in cubic centimeters (if known)."
  2. Changed6 schema fields changedv1.5.0
    • removedInput schema / properties / dimensions_x_mm / default
      Removed value: -null
    • removedInput schema / properties / dimensions_y_mm / default
      Removed value: -null
    • removedInput schema / properties / dimensions_z_mm / default
      Removed value: -null
    • removedInput schema / properties / quantity / default
      Removed value: -1
    • addedInput schema / properties / quantity / description
      Added value: +"Default: 1."
    • removedInput schema / properties / volume_cm3 / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A4.3/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 genuinely useful behavior beyond that: the return is a low/high range derived from typical per-cm3 pricing, which signals the output is a ballpark rather than a binding number, and it points to fulfillment_quote for exactness.

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 purpose and the fulfillment_quote handoff are front-loaded, and the closing constraint sentence is the most operationally important detail. The Args block largely restates schema descriptions line-for-line, which is mild padding for a tool whose schema is already richly documented in the same response.

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 a read-only, no-output-schema tool, the definition covers purpose, alternative, return shape (low/high range), and the input-combination rule. It could still say how quantity interacts with the range or whether dimensions are used to infer volume, but nothing essential to calling it correctly is missing.

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?

Schema description coverage is 100%, so parameter meanings are already documented and the baseline is 3. The description earns an extra point by stating a cross-parameter constraint that the schema does not encode: either volume_cm3 or all three dimension parameters must be supplied. That is a real invocation rule not derivable from the required list, which names only technology.

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 states a specific verb and resource ("Get an instant price estimate") and immediately positions it relative to a named sibling, "fulfillment_quote", for exact pricing. An agent can distinguish the cheap pre-quote estimate from the real-model quote without opening either schema.

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 clearly says when to use it ("before requesting a full quote") and names the alternative for the exact-pricing case. It does not differentiate from other estimate-flavored siblings such as estimate_cost, estimate_print_cost_from_mesh, or print_service_quote, so routing among those is still left 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