Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

explain_calibration_for_design

Read-only

Explain in plain English which calibration offsets were applied to a design, printer, or material, optionally filtered by feature class, nominal size, or recipe version.

Instructions

Plain-English explanation of which calibration offsets were applied.

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explain_calibration_for_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoRequired when ``design_id`` is empty or no slice history exists. Default: "".
design_idNoThe design slug. When supplied, the tool resolves printer + material from the slice history; the explicit params below are ignored. Default: "".
printer_idNoRequired when ``design_id`` is empty or no slice history exists. Default: "".
feature_classNoOnly explain offsets for this kind of feature (``hole``, ``pin``, ``slot`` ..., as recorded by ``ingest_measurement``). Empty explains every kind. Default: "".
recipe_versionNoOptional pin — when supplied, picks the most-recent slice of THIS specific recipe version (e.g. ``"v3"``). Default uses the latest slice of the design across all versions. Default: "".
nominal_size_mmNoOnly explain the offset recorded at this designed size, in mm; needs ``feature_class``. 0 (the default) explains every size. Default: 0.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"The design slug.  When supplied, the tool resolves printer + material from the slice history; the explicit params below are ignored. Default: \"\"."
    • changedInput schema / properties / feature_class / description
      Previous value: -"Default: \"\"."New value: +"Only explain offsets for this kind of feature (``hole``, ``pin``, ``slot`` ..., as recorded by ``ingest_measurement``).  Empty explains every kind. Default: \"\"."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Required when ``design_id`` is empty or no slice history exists. Default: \"\"."
    • changedInput schema / properties / nominal_size_mm / description
      Previous value: -"Default: 0.0."New value: +"Only explain the offset recorded at this designed size, in mm; needs ``feature_class``.  0 (the default) explains every size. Default: 0.0."
    • changedInput schema / properties / printer_id / description
      Previous value: -"Default: \"\"."New value: +"Required when ``design_id`` is empty or no slice history exists. Default: \"\"."
    • changedInput schema / properties / recipe_version / description
      Previous value: -"Default: \"\"."New value: +"Optional pin — when supplied, picks the most-recent slice of THIS specific recipe version (e.g. ``\"v3\"``).  Default uses the latest slice of the design across all versions. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/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 the safety profile is covered. The description adds one genuinely useful piece beyond that: the tool requires a Kiln Pro entitlement, which an agent needs to know before calling. It does not, however, describe the shape of the explanation returned or behavior when the design has no slice history.

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?

Two short, front-loaded lines with no filler: purpose first, prerequisite second. It is efficient, though so terse that the prerequisite is the only secondary information conveyed.

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?

Invocation is fully specified by the schema (six optional params with documented interplay) and safety by annotations, so the basics are covered. However, this is an explanation-producing tool with no output schema, and the description says nothing about the form of the plain-English output, so an agent cannot predict the return shape.

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%, and the parameter descriptions are unusually rich, explaining that design_id resolves printer and material from slice history and overrides the explicit params, and that nominal_size_mm requires feature_class. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (explain) and a specific resource (calibration offsets that were applied), and the name scopes it to a design. It is clear what the tool produces, though it never distinguishes itself from calibration siblings such as query_per_machine_offset or assess_calibration_status.

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?

The only usage signal is the 'Needs Kiln Pro' note, which is an entitlement gate rather than guidance. There is no statement of when to use this versus query_per_machine_offset, assess_calibration_status, or apply_calibration_recommendations, and no note on what to do when no slice history exists.

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