Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

assess_calibration_status

Read-only

Assess calibration confidence for slicer profiles and auto-import matching profiles, highlighting material gaps before printing.

Instructions

Calibration confidence + auto-import for slicer profiles.

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

Input Schema

NameRequiredDescriptionDefault
modeNo"normie" | "engineer" | "auto". Default: "auto".
briefNoOptional user request brief (auto-detects engineer mode if it contains FoS / sigma / ISO 286 / etc.).
printer_idNoPrinter identifier (e.g. "bambu_a1") whose slicer profiles to assess. Omit to assess every profile found.
intended_materialNoThe material you're about to print. If it doesn't match the calibrated material, the coaching message highlights the gap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / brief / description
      Added value: +"Optional user request brief (auto-detects engineer mode if it contains FoS / sigma / ISO 286 / etc.)."
    • addedInput schema / properties / intended_material / description
      Added value: +"The material you're about to print. If it doesn't match the calibrated material, the coaching message highlights the gap."
    • changedInput schema / properties / mode / description
      Previous value: -"Default: \"auto\"."New value: +"\"normie\" | \"engineer\" | \"auto\". Default: \"auto\"."
    • addedInput schema / properties / printer_id / description
      Added value: +"Printer identifier (e.g. \"bambu_a1\") whose slicer profiles to assess.  Omit to assess every profile found."
  2. Addedv1.5.0

TDQS

C2.4/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says 'auto-import for slicer profiles,' which implies a write/import side effect. This is a direct contradiction of the read-only annotation, so the description cannot be trusted for behavioral disclosure.

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 description is very short and front-loads the domain, with no wasted words. However, the phrasing 'Calibration confidence + auto-import' is cryptic and could be structured more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with four parameters and no output schema, the description is far too sparse. It does not explain what the assessment returns, what 'auto-import' actually does, or how the mode and brief parameters affect behavior.

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 input schema already documents all four parameters. The description adds no parameter-level meaning beyond the schema, which is acceptable at baseline when the schema is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the domain (calibration confidence, slicer profiles) but does not state a clear verb or scope for the assessment. It also fails to distinguish this tool from nearby siblings such as classify_calibration_confidence or get_calibration_freshness.

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 guidance on when to use this tool versus alternatives, nor any exclusions or preconditions beyond the vague 'Needs Kiln Pro' note. The agent is left to infer usage from the name alone.

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