Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

validate_assembly

Read-only

Validate an assembly for correctness and printability by running clearance and joint checks and returning updated results. Optionally include printer-specific screw-hole data for fitted joints.

Instructions

Validate an assembly for correctness and printability.

        Runs clearance checks and joint validations on the assembly,
        returning the validated assembly state with results populated.

        Args:
            assembly_json: JSON string of the current assembly state.
            printer_id: Optional printer model id (e.g.
                ``"bambu_a1"``).  With it, each joint that drives a
                screw into a printed part gains a ``screw_hole`` block
                (compensated hole diameter, thread engagement,
                install-torque ceiling, lead-in chamfer) tuned for that
                machine where Kiln has data, else a generic starting
                point.  Omit it for the plain validation.

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": {
      "assembly_json": "<assembly_json>"
    },
    "name": "validate_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_idNoOptional printer model id (e.g. ``"bambu_a1"``). With it, each joint that drives a screw into a printed part gains a ``screw_hole`` block (compensated hole diameter, thread engagement, install-torque ceiling, lead-in chamfer) tuned for that machine where Kiln has data, else a generic starting point. Omit it for the plain validation.
assembly_jsonYesJSON string of the current assembly state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / assembly_json / description
      Added value: +"JSON string of the current assembly state."
    • addedInput schema / properties / printer_id / description
      Added value: +"Optional printer model id (e.g. ``\"bambu_a1\"``).  With it, each joint that drives a screw into a printed part gains a ``screw_hole`` block (compensated hole diameter, thread engagement, install-torque ceiling, lead-in chamfer) tuned for that machine where Kiln has data, else a generic starting point.  Omit it for the plain validation."
  2. Changed3 schema fields changedv1.5.0
    • addedInput schema / properties / assembly_json / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
    • removedInput schema / properties / assembly_json / type
      Removed value: -"string"
    • removedInput schema / properties / printer_id / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, closed-world operation. Beyond that, the description usefully discloses that it runs clearance checks and joint validations and returns the validated assembly state with results populated, plus how printer_id enriches screw-joint validation output.

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 is front-loaded and the optional printer_id behavior is explained clearly. The formatting is somewhat verbose and duplicates schema text, but it remains readable and does not bury the main operation.

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 two-parameter validation tool with annotations and no output schema, the description gives enough context about checks performed, return state, and optional printer-specific enrichment. It could be stronger by explicitly positioning the tool against related assembly-validation siblings.

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 both parameters are already documented in the schema. The description repeats the same parameter meaning, especially for printer_id, without adding syntax or format details beyond what the structured schema 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?

The description states a specific verb and resource: validate an assembly for correctness and printability, with clearance checks and joint validations. It is clear what the tool does, but it does not distinguish itself from closely related siblings such as check_assembly_clearances or check_assembly_stands.

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?

The description implies when to use it by saying it validates assemblies for correctness and printability, and it explains the effect of including printer_id. However, it gives no explicit guidance on when to choose this tool over related assembly-checking or printability-analysis siblings.

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