Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

advise_kit_scale

Read-only

Calculate a shared print scale so every part in a kit fits the target 3D printer bed and nozzle limits, keeping the full set printable.

Instructions

Find the largest scale at which EVERY part of a kit prints.

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": {
      "part_paths": "<part_paths>"
    },
    "name": "advise_kit_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
bed_x_mmNoBed width (default 256). Default: 256.0.
bed_y_mmNoBed depth (default 256). Default: 256.0.
bed_z_mmNoBed height (default 256). Default: 256.0.
nozzle_mmNoNozzle diameter — sets the feature floor. Leave unset for the only printer Kiln knows of, else 0.4; ``nozzle`` in the reply says which.
part_pathsYesOne mesh file per part (the import_model_parts output).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / bed_x_mm / description
      Previous value: -"Default: 256.0."New value: +"Bed width (default 256). Default: 256.0."
    • changedInput schema / properties / bed_y_mm / description
      Previous value: -"Default: 256.0."New value: +"Bed depth (default 256). Default: 256.0."
    • changedInput schema / properties / bed_z_mm / description
      Previous value: -"Default: 256.0."New value: +"Bed height (default 256). Default: 256.0."
    • addedInput schema / properties / nozzle_mm / description
      Added value: +"Nozzle diameter — sets the feature floor. Leave unset for the only printer Kiln knows of, else 0.4; ``nozzle`` in the reply says which."
    • addedInput schema / properties / part_paths / description
      Added value: +"One mesh file per part (the import_model_parts output)."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly=true, destructive=false and openWorld=false, so safety is covered and the bar is lower. The description adds the meaningful constraint that ALL parts must fit (not just one), but says nothing about what happens when no valid scale exists, how orientation is treated, or what form the answer takes — gaps that matter for a computational advisor tool.

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 the key constraint (EVERY) emphasized in caps — lean and easy to scan. It borders on under-specification for a five-parameter tool, but there is no wasted wording.

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 a moderate-complexity advisor taking bed dimensions, a nozzle floor and a list of parts; the description conveys the goal but not the decision logic or outcome shape. Since no output schema exists, the description could reasonably say what the reply contains (the scale, the nozzle used), but it leaves that to the parameter text.

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 bed dimensions, nozzle diameter and part_paths are already documented in the schema, setting the baseline at 3. The description's phrase 'EVERY part' reinforces that part_paths is a collection that must all fit, but it adds no meaning about bed/nozzle parameters beyond what the schema already provides.

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?

States a specific verb and resource — find the largest scale at which every part of a kit prints — which is a clear, unambiguous operation an agent can recognize. It does not explicitly name sibling alternatives (e.g. scale_mesh_to_fit, split_mesh_to_fit, plan_kit_plates), so the differentiation is only implied by the word 'kit'.

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?

Usage is implied: you call this when you have a multi-part kit and want the maximum print scale that keeps all parts fitting. There is no explicit statement of when not to use it, no mention of the single-part alternative (scale_mesh_to_fit), and no prerequisites such as requiring import_model_parts output first, even though the schema hints at it.

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