Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_assembly_clearances

Read-only

Checks clearances between all mating parts in an assembly and reports whether each interface meets its required clearance gap, applying a default gap when none is specified.

Instructions

Check clearances between all mating parts in an assembly.

        Returns a list of clearance check results indicating whether
        each interface meets its clearance requirements.

        Args:
            assembly_json: JSON string of the current assembly state.
            default_clearance_mm: Default clearance gap in mm to use
                when an interface does not specify one (default 0.2).

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": "check_assembly_clearances"
  }
}

Input Schema

NameRequiredDescriptionDefault
assembly_jsonYesJSON string of the current assembly state.
default_clearance_mmNoDefault clearance gap in mm to use when an interface does not specify one (default 0.2). Default: 0.2.

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."
    • changedInput schema / properties / default_clearance_mm / description
      Previous value: -"Default: 0.2."New value: +"Default clearance gap in mm to use when an interface does not specify one (default 0.2). Default: 0.2."
  2. Changed4 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 / default_clearance_mm / default
      Removed value: -0.2
    • addedInput schema / properties / default_clearance_mm / description
      Added value: +"Default: 0.2."
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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 safety is covered. The description adds genuine context beyond that: it discloses the return shape ('a list of clearance check results indicating whether each interface meets its clearance requirements') and the fallback rule that interfaces without a specified clearance use the default gap.

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 return behavior are front-loaded in two short sentences, which is good structure. The reStructuredText Args block duplicates the schema descriptions and could be dropped, but the overall length is modest and not padded.

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, read-only analysis tool with no output schema, the definition supplies what an agent needs: what is measured, what is returned, and how the default clearance is applied. It falls short only on workflow positioning relative to other assembly tools.

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, and the Args block largely restates those descriptions verbatim. It adds only the note that the default applies when an interface does not specify a clearance, which is a minor semantic clarification rather than new meaning.

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 first sentence states a specific verb and resource: 'Check clearances between all mating parts in an assembly.' An agent can tell it measures clearances rather than validating or composing an assembly. It does not explicitly name near-sibling alternatives such as validate_assembly or check_assembly_stands, so it stops short of a 5.

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 statement of when to use this versus alternatives, no prerequisites (does the assembly need to be composed first?), and no exclusions. 'Between all mating parts in an assembly' implies the tool operates on an assembly state but gives no decision guidance for an agent choosing among validate_assembly, check_assembly_stands, or check_multi_material_pairing.

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