Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

classify_calibration_confidence

Read-only

Assess how far to trust each calibration setting and the overall print profile by classifying confidence from profile values and history.

Instructions

Say how far to trust each calibration setting, and the profile as a whole.

Needs Kiln Pro.

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": {
      "tool_name": "<tool_name>"
    },
    "name": "classify_calibration_confidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
tool_nameYesSlicer / CAM / laser-controller identifier (``"orcaslicer"``, ``"bambustudio"``, ``"prusaslicer"``); a slicer Kiln does not know reads every setting as ``not_compared``.
parsed_fieldsNoThe profile's own values (``flow_rate``, ``pressure_advance``, ``xy_compensation_mm``, ``max_volumetric_speed_mm3s``, ``retraction_distance_mm``) and its history (``modification_timestamp_iso``, ``first_print_timestamp_iso``, ``sibling_profiles`` as a list of ``{"material_id", "flow_rate"}``, ``has_calibration_event_marker`` as a bool).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / parsed_fields / description
      Added value: +"The profile's own values (``flow_rate``, ``pressure_advance``, ``xy_compensation_mm``, ``max_volumetric_speed_mm3s``, ``retraction_distance_mm``) and its history (``modification_timestamp_iso``, ``first_print_timestamp_iso``, ``sibling_profiles`` as a list of ``{\"material_id\", \"flow_rate\"}``, ``has_calibration_event_marker`` as a bool)."
    • addedInput schema / properties / tool_name / description
      Added value: +"Slicer / CAM / laser-controller identifier (``\"orcaslicer\"``, ``\"bambustudio\"``, ``\"prusaslicer\"``); a slicer Kiln does not know reads every setting as ``not_compared``."
  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 real value beyond that by disclosing the Kiln Pro entitlement requirement, which annotations cannot express. It stops short of describing how confidence is derived, what thresholds or categories are produced, or the cost/latency profile of the call.

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 sentences, front-loaded with the purpose and followed by the entitlement constraint; nothing is padded or redundant. The terse phrasing ('Say how far to trust') is a little informal for a classification tool but costs no clarity.

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?

With no output schema, the description carries the burden of explaining what comes back, and it only implies a confidence rating without naming categories, score ranges, or whether per-setting and profile-level results are separate fields. For a tool whose entire value is the returned judgment, that is a meaningful gap, though the input side is fully documented by the schema.

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 parsed_fields property already enumerates the keys it accepts (flow_rate, pressure_advance, timestamps, sibling_profiles, calibration event marker). The description adds no syntax, format, or optionality guidance beyond the schema, so it sits at the baseline for a well-documented schema.

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 concrete action on a concrete resource: rate how trustworthy each calibration setting is, plus the profile overall. An agent can tell this is a confidence-scoring tool rather than a settings-mutator. It does not differentiate itself from near-siblings such as assess_calibration_status, get_calibration_freshness, or get_calibration_health_recommendations, which also judge calibration quality.

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 context given is the prerequisite 'Needs Kiln Pro', which is genuinely useful gating information. There is no guidance on when to call this versus the several calibration-assessment siblings, no statement of what inputs must be gathered first (e.g. where parsed_fields come from), and no exclusions.

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