Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

set_nozzle_state

Destructive

Records the nozzle installed on a 3D printer—material, diameter, install date and filament throughput—so the printer's reported nozzle can be compared with the new record.

Instructions

Record a user-entered nozzle state for a printer.

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": {
      "printer_id": "<printer_id>"
    },
    "name": "set_nozzle_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoOne of ``brass``, ``stainless_steel``, ``hardened_steel``, ``ruby_tip``, ``cht_brass``, ``cht_hardened``, ``tungsten_carbide``, ``custom``. Case-insensitive; ``unknown`` clears it.
printer_idYesStable printer identifier.
diameter_mmNoNozzle diameter in mm (typically 0.2, 0.25, 0.4, 0.6, 0.8, or 1.0).
install_dateNoISO 8601 date the nozzle was installed (e.g. ``"2026-05-26"``).
grams_throughNoCumulative grams already extruded through this nozzle. Usually omitted on a fresh swap.
printer_readingNoWhat the printer itself reports as its nozzle, filled in by the caller's own Kiln when it can reach the machine, so the answer can say whether the printer agrees with the new record. Used only where this process cannot read the printer; leave it unset by hand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • addedInput schema / properties / diameter_mm / description
      Added value: +"Nozzle diameter in mm (typically 0.2, 0.25, 0.4, 0.6, 0.8, or 1.0)."
    • addedInput schema / properties / grams_through / description
      Added value: +"Cumulative grams already extruded through this nozzle.  Usually omitted on a fresh swap."
    • addedInput schema / properties / install_date / description
      Added value: +"ISO 8601 date the nozzle was installed (e.g. ``\"2026-05-26\"``)."
    • addedInput schema / properties / material / description
      Added value: +"One of ``brass``, ``stainless_steel``, ``hardened_steel``, ``ruby_tip``, ``cht_brass``, ``cht_hardened``, ``tungsten_carbide``, ``custom``. Case-insensitive; ``unknown`` clears it."
    • addedInput schema / properties / printer_id / description
      Added value: +"Stable printer identifier."
    • addedInput schema / properties / printer_reading / description
      Added value: +"What the printer itself reports as its nozzle, filled in by the caller's own Kiln when it can reach the machine, so the answer can say whether the printer agrees with the new record.  Used only where this process cannot read the printer; leave it unset by hand."
  2. Addedv1.5.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, but the description says only "Record," which reads like a benign append rather than an overwrite of an existing nozzle record. It adds nothing about what existing data is replaced, what "unknown" clearing means, or how printer_reading affects the outcome — the safety-relevant behavior is left entirely to annotations and schema.

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?

A single front-loaded sentence with no wasted words; the qualifier "user-entered" appears early. It is terse to the point of under-specification, but nothing is padded or redundant.

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 six parameters, a nested object, no output schema, and a destructive write, the definition covers the bare minimum only because the schema is richly documented. Nothing in the description explains overwrite semantics or the role of printer_reading in the result, leaving a gap for a mutation tool.

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 schema already explains printer_id, material enums, diameter, install_date, grams_through, and printer_reading in detail. The description adds no parameter meaning beyond that baseline, which is the expected floor when the schema is fully documented.

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 gives a concrete verb and resource ("Record ... nozzle state") and qualifies the source as "user-entered," which distinguishes manual entry from siblings like auto_detect_nozzle. It does not name or contrast with get_nozzle_state, list_nozzle_states, or record_nozzle_replacement, so the differentiation is only partial.

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 instead of auto_detect_nozzle, get_nozzle_state, or record_nozzle_replacement, and no prerequisites or exclusions. The word "user-entered" hints at manual use but the agent must infer the actual selection criteria.

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