Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_joint_recommendation

Read-only

Returns clearance recommendations for a joint type and material pairing, optionally narrowing the range using a printer identifier and calibration data.

Instructions

Get recommended clearance settings for a joint type and material pairing.

        Returns clearance recommendations based on the joint type
        and the materials of the two mating parts.  When
        ``printer_id`` is supplied AND kiln-pro is installed, the
        response narrows the clearance range by the user's
        calibration tier (HIGH halves it, MEDIUM shaves ~10%, LOW
        and UNKNOWN leave it unchanged) and attaches a
        ``calibration_used`` block documenting the source.

        Args:
            joint_type: Type of joint (e.g. ``"clearance_fit"``,
                ``"press_fit"``, ``"snap_fit"``).
            material_a: Material of the first part (default ``"PLA"``).
            material_b: Material of the second part (default ``"PLA"``).
            printer_id: Optional printer identifier (e.g.
                ``"bambu_a1"``).  For a joint whose parts MOVE, omitting
                it resolves the user's active printer rather than
                answering generically — pass it only to ask about a
                machine that is not the one they are set up on.  For
                every other joint type, omitting it keeps the historic
                flat-range behaviour.
            mating: Optional shape hint for joints whose parts MOVE
                against each other (``"clearance_fit"``, ``"loose"``):
                ``"pin_in_bore"`` for a shaft or pin turning in a hole,
                ``"slot"`` for a tongue sliding in a groove,
                ``"planar_face"`` for two flat faces sliding, or
                ``"gear_flank"`` for meshing teeth.  Omitted, the
                round-joint case is assumed, the reading that errs loose
                rather than tight.  Ignored for joints that do not move.

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": {
      "joint_type": "<joint_type>"
    },
    "name": "get_joint_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
matingNoOptional shape hint for joints whose parts MOVE against each other (``"clearance_fit"``, ``"loose"``): ``"pin_in_bore"`` for a shaft or pin turning in a hole, ``"slot"`` for a tongue sliding in a groove, ``"planar_face"`` for two flat faces sliding, or ``"gear_flank"`` for meshing teeth. Omitted, the round-joint case is assumed, the reading that errs loose rather than tight. Ignored for joints that do not move.
joint_typeYesType of joint (e.g. ``"clearance_fit"``, ``"press_fit"``, ``"snap_fit"``).
material_aNoMaterial of the first part (default ``"PLA"``). Default: "PLA".
material_bNoMaterial of the second part (default ``"PLA"``). Default: "PLA".
printer_idNoOptional printer identifier (e.g. ``"bambu_a1"``). For a joint whose parts MOVE, omitting it resolves the user's active printer rather than answering generically — pass it only to ask about a machine that is not the one they are set up on. For every other joint type, omitting it keeps the historic flat-range behaviour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • addedInput schema / properties / joint_type / description
      Added value: +"Type of joint (e.g. ``\"clearance_fit\"``, ``\"press_fit\"``, ``\"snap_fit\"``)."
    • changedInput schema / properties / material_a / description
      Previous value: -"Default: \"PLA\"."New value: +"Material of the first part (default ``\"PLA\"``). Default: \"PLA\"."
    • changedInput schema / properties / material_b / description
      Previous value: -"Default: \"PLA\"."New value: +"Material of the second part (default ``\"PLA\"``). Default: \"PLA\"."
    • addedInput schema / properties / mating / description
      Added value: +"Optional shape hint for joints whose parts MOVE against each other (``\"clearance_fit\"``, ``\"loose\"``): ``\"pin_in_bore\"`` for a shaft or pin turning in a hole, ``\"slot\"`` for a tongue sliding in a groove, ``\"planar_face\"`` for two flat faces sliding, or ``\"gear_flank\"`` for meshing teeth.  Omitted, the round-joint case is assumed, the reading that errs loose rather than tight.  Ignored for joints that do not move."
    • addedInput schema / properties / printer_id / description
      Added value: +"Optional printer identifier (e.g. ``\"bambu_a1\"``).  For a joint whose parts MOVE, omitting it resolves the user's active printer rather than answering generically — pass it only to ask about a machine that is not the one they are set up on.  For every other joint type, omitting it keeps the historic flat-range behaviour."
  2. Changed6 schema fields changedv1.5.0
    • removedInput schema / properties / material_a / default
      Removed value: -"PLA"
    • addedInput schema / properties / material_a / description
      Added value: +"Default: \"PLA\"."
    • removedInput schema / properties / material_b / default
      Removed value: -"PLA"
    • addedInput schema / properties / material_b / description
      Added value: +"Default: \"PLA\"."
    • removedInput schema / properties / mating / default
      Removed value: -null
    • removedInput schema / properties / printer_id / default
      Removed value: -null
  3. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / mating
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Mating"
+}
  4. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses real behavioral traits: the result is narrowed by calibration tier with specific magnitudes (HIGH halves the range, MEDIUM shaves ~10%, LOW/UNKNOWN unchanged), the narrowing only happens when kiln-pro is installed, and a calibration_used block is attached documenting the source. It also states the default-to-loose fallback for the omitted mating hint. That is exactly the kind of conditional behavior an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and calibration-tier behavior are front-loaded, which is good, but the bulk of the body is an Args block duplicating parameter descriptions that already exist at 100% coverage in the schema. Roughly half the text is redundant restatement, diluting the genuinely valuable conditional behavior sentences.

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?

With no output schema, the description carries the return burden and does explain that a clearance recommendation is returned plus, conditionally, a calibration_used block. It also covers the kiln-pro dependency and the tier-dependent narrowing. Missing only a sense of output shape (range units, how many candidate values) and how this differs from adjacent recommendation 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 the baseline is 3, and the Args section largely restates the schema text verbatim (joint_type, material_a/b, printer_id, mating appear in near-identical wording). The only genuine added meaning, the printer_id active-printer resolution rule, is already present in the schema as well, so the description adds little beyond the structured fields.

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: 'Get recommended clearance settings for a joint type and material pairing', and the body clarifies it returns clearance ranges derived from joint type and the two mating materials. It is clearly distinguishable from most siblings, but it never names or contrasts itself with the closest ones (recommend_joint_strategy, recommend_running_clearance, compute_iso_fit), so the agent must infer the boundary.

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 through conditional prose ('When printer_id is supplied AND kiln-pro is installed...', 'pass it only to ask about a machine that is not the one they are set up on'), which tells the agent how to steer behavior but not when to pick this tool over the several clearance/joint recommendation siblings. No explicit when-not or alternative routing is given.

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