Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

estimate_batch_cost

Read-only

Calculates total production cost for a batch of decorated items using per-item decoration cost, unit count, setup time, and labor rate.

Instructions

Estimate total cost for a batch of decorated items (Pro).

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": {
      "num_units": "<num_units>",
      "decoration_cost": "<decoration_cost>"
    },
    "name": "estimate_batch_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
num_unitsYesNumber of units in the batch.
decoration_costYesThe answer ``estimate_decoration_cost`` gave for one item, passed back as it came.
setup_time_minutesNoOne-time setup time in minutes (default 5). Default: 5.0.
labor_cost_per_hourNoHourly labor rate (default 0). Default: 0.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / decoration_cost / description
      Added value: +"The answer ``estimate_decoration_cost`` gave for one item, passed back as it came."
    • changedInput schema / properties / labor_cost_per_hour / description
      Previous value: -"Default: 0.0."New value: +"Hourly labor rate (default 0). Default: 0.0."
    • addedInput schema / properties / num_units / description
      Added value: +"Number of units in the batch."
    • changedInput schema / properties / setup_time_minutes / description
      Previous value: -"Default: 5.0."New value: +"One-time setup time in minutes (default 5). Default: 5.0."
  2. Addedv1.5.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds only the '(Pro)' tier signal and the notion of batching, which is modest value. It does not say whether setup time and labor are folded in, whether results are per-batch or per-unit, or how the calculation treats the passthrough decoration cost payload.

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?

A single front-loaded sentence with no wasted words, which is appropriate for a narrow estimator. The only weakness is that so little is said that compactness shades into under-specification, and '(Pro)' reads as an unresolved tag.

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?

The tool is read-only with a fully documented four-parameter schema and no output schema, so the description needn't explain return values. Still, for a cost estimator nested in a dense sibling cluster, it should state the estimate_decoration_cost prerequisite and whether material cost is included. Those gaps leave it only minimally adequate.

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 all four parameters including the defaulted setup_time_minutes and labor_cost_per_hour are documented inline. The description adds nothing beyond that baseline. It does not clarify the meaning of the opaque nested decoration_cost object, though the schema's own wording carries that burden.

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 says it estimates total cost for a batch of decorated items, which gives a verb and a resource. But it is thin on scope details (what cost components are included, whether material is counted) and does not distinguish itself from near-siblings such as estimate_decoration_cost, estimate_cost, or batch_estimate_plate_part_costs. The trailing '(Pro)' hints at a tier gate but is unexplained.

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 use this versus estimate_decoration_cost or the other cost estimators. Critically, the required chaining from estimate_decoration_cost output is only discoverable in the schema text for decoration_cost, not in the description. No exclusions or prerequisites are stated.

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