Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_nozzle_capacity_for_print

Read-only

Check whether a planned print's filament weight and material will stay within the nozzle's wear capacity before printing.

Instructions

Pre-print check — will the nozzle survive this print's wear cost?

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>",
      "planned_grams": "<planned_grams>"
    },
    "name": "check_nozzle_capacity_for_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_idYesActive printer identifier.
planned_gramsYesEstimated filament weight for the upcoming print, in grams.
printer_modelNoOptional model lookup key for the factory-default fallback when the printer has no recorded state. Default: "".
filament_materialNoThe filament being printed (``"PETG-CF"``, ``"Wood-PLA"``, ``"PLA"``); it decides whether the print counts as abrasive. Omitted, the answer assumes a non-abrasive filament and says it was not told, so pass it. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / filament_material / description
      Previous value: -"Default: \"\"."New value: +"The filament being printed (``\"PETG-CF\"``, ``\"Wood-PLA\"``, ``\"PLA\"``); it decides whether the print counts as abrasive.  Omitted, the answer assumes a non-abrasive filament and says it was not told, so pass it. Default: \"\"."
    • addedInput schema / properties / planned_grams / description
      Added value: +"Estimated filament weight for the upcoming print, in grams."
    • addedInput schema / properties / printer_id / description
      Added value: +"Active printer identifier."
    • changedInput schema / properties / printer_model / description
      Previous value: -"Default: \"\"."New value: +"Optional model lookup key for the factory-default fallback when the printer has no recorded state. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, non-destructive check, lowering the disclosure burden. The description adds the concept of wear-cost survival but does not explain what the check compares, what state it relies on, or what happens when nozzle state is missing.

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 definition is a single front-loaded sentence with no filler, and the essential pre-print context comes first. The question form and phrase 'wear cost' are slightly less direct than a declarative statement would be.

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?

There is no output schema, yet the description does not explain what result is returned, how capacity or survival is expressed, or what an agent should do with the answer. For a pre-print decision tool with optional fallback and material-dependent behavior documented only in the schema, this is too sparse to be complete.

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 four parameters already have clear definitions, including the optional fallback model and filament abrasive assumption. The description adds no additional parameter meaning beyond what the schema provides.

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 pre-print check about whether the nozzle can survive the print's wear cost, which is a clear resource and action. It does not explicitly differentiate itself from sibling nozzle-state tools such as get_nozzle_state or nozzle_wear_status.

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?

The phrase 'Pre-print check' implies it should be used before starting a print, but there is no explicit when-to-use guidance, exclusions, or named alternatives. The agent must infer its place among several adjacent nozzle and readiness tools.

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