Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

nozzle_drift_attribution

Read-only

Attribute observed dimensional or flow drift, or a failure hypothesis, to nozzle wear using printer wear state, drift magnitude, and filament abrasiveness.

Instructions

Pro+ — attribute observed drift OR a failure hypothesis to nozzle wear.

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

Input Schema

NameRequiredDescriptionDefault
drift_kindNoOne of ``"dimensional"`` (XY/Z geometry), ``"flow"`` (extrusion rate), or ``"unknown"`` (the default, when you cannot tell). Drives the per-component routing. Default: "unknown".
printer_idYesActive printer identifier.
percent_usedNoOptional pre-computed wear fraction. When omitted, falls back to ``assess_wear`` on the resolved nozzle state.
drift_magnitude_mmNoAbsolute size of the observed drift in millimetres. ``None`` switches to hypothesis mode.
recent_filament_classNo``"abrasive"`` or ``"standard"`` — abrasive filaments raise the prior on wear-attributability. Default: "standard".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.1
    • changedInput schema / properties / drift_kind / description
      Previous value: -"Default: \"unknown\"."New value: +"One of ``\"dimensional\"`` (XY/Z geometry), ``\"flow\"`` (extrusion rate), or ``\"unknown\"`` (the default, when you cannot tell). Drives the per-component routing. Default: \"unknown\"."
    • addedInput schema / properties / drift_magnitude_mm / description
      Added value: +"Absolute size of the observed drift in millimetres.  ``None`` switches to hypothesis mode."
    • addedInput schema / properties / percent_used / description
      Added value: +"Optional pre-computed wear fraction. When omitted, falls back to ``assess_wear`` on the resolved nozzle state."
    • addedInput schema / properties / printer_id / description
      Added value: +"Active printer identifier."
    • changedInput schema / properties / recent_filament_class / description
      Previous value: -"Default: \"standard\"."New value: +"``\"abrasive\"`` or ``\"standard\"`` — abrasive filaments raise the prior on wear-attributability. Default: \"standard\"."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful context about the Pro+ tier and the two attribution modes, but it does not explain the result, confidence, or interpretation of the attribution.

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 a single front-loaded sentence with no wasted wording. It is very terse, but the core purpose is immediately clear.

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?

The schema and annotations cover parameters and safety well, but the description does not explain the attribution output or how to choose this tool over related nozzle-wear tools. For a diagnostic tool with no output schema, that leaves a meaningful gap.

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 all five parameters are already well documented in the input schema. The description does not add meaning beyond the schema, which is acceptable at the baseline for high coverage.

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 and resource: attribute observed drift or a failure hypothesis to nozzle wear. It clearly conveys the diagnostic purpose, though it does not differentiate this tool from nearby siblings such as nozzle_wear_status or get_nozzle_state.

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?

It implies the tool is used when there is observed drift or a failure hypothesis to attribute, but it gives no explicit when-to-use versus alternatives and no exclusions. The usage context is present but minimal.

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