Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Update spool

update_spool
Destructive

Adjust or remove a filament spool in local inventory: set remaining grams, subtract grams used by a finished print, edit notes, or change its filament preset.

Instructions

Change a spool in the local inventory: set what's left, subtract a finished print, edit notes, or remove it.

use_g subtracts each time it is called, so don't repeat it for the same print. remove=true deletes the spool record permanently. Returns the updated spool.

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": {
      "spool_id": "<spool_id>"
    },
    "name": "update_spool"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoReplace the spool's notes.
use_gNoSubtract grams used by a finished print.
removeNoDelete the spool from the inventory.
spool_idYesSpool id from list_spools or add_spool.
remaining_gNoSet grams left, e.g. after weighing the spool.
filament_presetNoSet the filament preset to print it with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description earns credit by explaining WHY: use_g is cumulative and repeating it double-subtracts, and remove is permanent deletion of the record. It also states the return value ("Returns the updated spool"). It does not say whether a remove call still applies the other supplied fields or what happens to a missing spool_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs, front-loaded with the operation summary, then the two caveats that matter most. Every sentence carries operational information; nothing is padding.

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

Completeness4/5

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

For a six-parameter destructive mutation tool with no output schema, the description covers the mutation modes, the destructive path, the non-idempotent accounting trap, and the return value. The remaining gap is combination semantics (what remove=true does to simultaneously supplied fields) and error behavior for an unknown spool_id.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3 and the schema already documents all six parameters. The description adds behavioral meaning beyond the schema by framing use_g as an accumulator (repeated calls compound) and by pairing remove with permanent deletion, which the schema's one-line field descriptions do not convey.

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 names a specific verb and resource ("Change a spool in the local inventory") and enumerates the four supported modes: set remaining grams, subtract usage, edit notes, or remove. It is clearly the mutation counterpart to list_spools/add_spool (which are referenced in the spool_id schema), though it never explicitly states those alternatives in the description text.

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?

"use_g subtracts each time it is called, so don't repeat it for the same print" is a genuine when/how-to-use constraint that prevents a real error, and "remove=true deletes the spool record permanently" flags the irreversible path. It stops short of stating precedence when multiple operations are combined (e.g. remove plus notes) or when to prefer this over add_spool/deleting and re-adding.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.