Skip to main content
Glama

add_feature_during_print_fleet

Add the same feature, such as a hat, to multiple paused 3D printers at once so a fleet resumes together with consistent edits.

Instructions

Add the same feature (e.g. a hat) to N paused printers (Business+).

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": {
      "feature": "<feature>",
      "printers": "<printers>"
    },
    "name": "add_feature_during_print_fleet"
  }
}

Input Schema

NameRequiredDescriptionDefault
orientNo``"auto"`` (default, the slicer chooses), ``"identity"`` or ``"upright"``. Default: "auto".
featureYesPlain-language spec of the shape to add ("a small top hat", a mesh path, ``library:<name>``), the same on every printer.
bed_tempNoBed temperature, read and checked the same way as ``hotend_temp``.
printersYesRequired, non-empty: one spec dict per paused printer, as described above. Names must be unique (an entry without one is ``"default"``); duplicates are refused.
hotend_tempNoNozzle temperature for every printer's resume. Unset, each printer uses its own print's, read off its G-code.
filament_typeNoThe prints' material, applied to every printer. Unset, Kiln reads each print's own; a printer whose print names none is refused.
parent_design_idNoOptional design these prints derive from, recorded in each session's provenance. Default: "".
first_layer_height_mmNoFirst-layer height of the sliced feature, resting on each paused print's top face. Defaults to 0.2. Default: 0.2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.5.1
    • changedInput schema / properties / bed_temp / description
      Previous value: -"Default: 65."New value: +"Bed temperature, read and checked the same way as ``hotend_temp``."
    • addedInput schema / properties / feature / description
      Added value: +"Plain-language spec of the shape to add (\"a small top hat\", a mesh path, ``library:<name>``), the same on every printer."
    • changedInput schema / properties / filament_type / description
      Previous value: -"Default: \"PLA\"."New value: +"The prints' material, applied to every printer. Unset, Kiln reads each print's own; a printer whose print names none is refused."
    • changedInput schema / properties / first_layer_height_mm / description
      Previous value: -"Default: 0.2."New value: +"First-layer height of the sliced feature, resting on each paused print's top face. Defaults to 0.2. Default: 0.2."
    • changedInput schema / properties / hotend_temp / description
      Previous value: -"Default: 220."New value: +"Nozzle temperature for every printer's resume. Unset, each printer uses its own print's, read off its G-code."
    • changedInput schema / properties / orient / description
      Previous value: -"Default: \"auto\"."New value: +"``\"auto\"`` (default, the slicer chooses), ``\"identity\"`` or ``\"upright\"``. Default: \"auto\"."
    • changedInput schema / properties / parent_design_id / description
      Previous value: -"Default: \"\"."New value: +"Optional design these prints derive from, recorded in each session's provenance. Default: \"\"."
    • addedInput schema / properties / printers / description
      Added value: +"Required, non-empty: one spec dict per paused printer, as described above. Names must be unique (an entry without one is ``\"default\"``); duplicates are refused."
  2. Addedv1.5.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world mutation, and the description adds two useful facts: printers must be paused and the tier requirement. It says nothing about what happens on resume, that the feature is sliced and seated on each print's top face, or the refusal behavior for duplicate names / missing filament types, which the agent only learns from the 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 zero filler; the example ('e.g. a hat') aids comprehension cheaply. It is efficient, though borderline under-informative for a complex fleet mutation.

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 an 8-parameter, multi-printer mutation with no output schema and non-trivial failure modes (duplicate printer names, unresolvable filament type, non-paused targets), one sentence is insufficient. It omits the workflow position ('during print', requires pause, resumes encoding) and all error conditions.

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% with 8 well-documented parameters (orient, temps, filament_type defaults, uniqueness rules), so the schema does the heavy lifting. The description adds no parameter-level meaning of its own, which is acceptable but earns only the baseline.

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?

States a specific verb and resource ('Add the same feature ... to N paused printers') with scope (fleet-wide, same feature on every printer), which distinguishes it in spirit from the single-printer sibling add_feature_during_print. It never actually names that sibling, and 'feature' is left for the schema to define.

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?

Only an implicit precondition ('paused printers') and a tier gate ('Business+') are given. There is no guidance on when to use this versus add_feature_during_print, decorate_during_print_fleet, or deboss_during_print, and no note on ordering relative to resume.

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