Skip to main content
Glama

set_box_slot_filaments

Label the filament type, vendor, and color held in each Box slot on the printer. Preview the resolved values first, then confirm to write them; only named fields change.

Instructions

Tell the printer what filament is in each Box slot, in plain words. assignments is a list like [{"slot": 0, "filament": "PLA Matte", "color": "black"}, {"slot": 1, "filament": "PETG", "color": "#1353AB", "vendor": "Generic"}]. slot is 0-based across the Box (unit 1 = slots 0-3). Filament and vendor are names or ids from list_box_filament_options; color is a colour word, #RRGGBB or swatch id, and lands on the nearest of the printer's own swatches. Only the fields you name change; everything else is kept. The first call (no confirm) shows exactly what each name resolved to and what would be written; re-call with confirm=true to write it, and the values are read back. This labels spools for the printer; it moves no filament and does not change whether a slot holds filament. Refused during a print. Not yet verified on a physical Box.

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": {
      "assignments": "<assignments>"
    },
    "name": "set_box_slot_filaments"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
assignmentsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the two-phase preview-then-confirm flow, that values are read back after writing, that unspecified fields are preserved (partial update), that colours snap to the nearest printer swatch, that it is refused mid-print, and that it is unverified on physical hardware. These are exactly the operational traits an agent needs and none are derivable from readOnlyHint/idempotentHint/destructiveHint.

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?

Front-loaded with the purpose, then prerequisites, then the confirm protocol, then caveats — a sensible ordering with no filler. It runs long, and the example payload plus the swatch-snapping detail could be tightened, but nearly every clause adds decision-relevant information.

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

Completeness5/5

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

For a two-parameter write tool with an output schema (so return shape needn't be described), the definition covers input format, validation sources, safety gating, side effects, and a reliability caveat. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — `assignments` is an untyped array of open objects and `confirm` is an undescribed boolean — so the description carries the full burden and does: it gives a concrete example object, explains that slot is 0-based with unit 1 covering slots 0-3, defines acceptable filament/vendor references and colour formats, and clarifies that `confirm` triggers the write step. This is a textbook compensation for an empty schema.

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

Purpose5/5

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

States a specific verb and resource — labelling which filament is in each Box slot — and immediately distinguishes itself from the physical-load siblings by saying it 'moves no filament and does not change whether a slot holds filament.' An agent can tell it apart from load_box_slot or set_box_option without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditions: filament/vendor values must come from list_box_filament_options, and the tool is 'Refused during a print.' It also rules out the obvious misreading by denying that it loads filament. It stops short of explicitly naming the sibling to use instead when the agent actually wants to load a spool, leaving that inference to the reader.

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