Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Add spool

add_spool

Record a new spool in your local filament inventory, capturing material, colour, brand, price and remaining grams. Each entry gets a unique id and is saved to a JSON file on your computer.

Instructions

Record a new spool in the user's local filament inventory.

Use it when the user buys or opens a spool; create_filament_profile can also add one when saving a profile. Each call adds another spool with a new id, stored in a JSON file on this computer. Returns the 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": {
      "material": "<material>"
    },
    "name": "add_spool"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand.
notesNoFree-text notes, e.g. where it's stored or when it was dried.
priceNoPrice paid.
total_gNoNet weight of a full spool in grams.
materialYesMaterial, e.g. 'PLA' or 'PETG'.
colour_hexNoColour as '#RRGGBB'.
colour_nameNoColour name.
remaining_gNoGrams left now, if not full.
filament_presetNoFilament preset to print it with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag non-readonly, non-idempotent, closed-world, non-destructive; the description adds real value beyond them by disclosing that every call mints a new id (reinforcing non-idempotency), that data persists to a JSON file on this computer, and that the created spool is returned.

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?

Three short sentences, front-loaded with the action, then the trigger/alternative, then the side effects and return value; no filler and no repetition of schema content.

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 nine-parameter mutation with full schema coverage and no output schema, the description covers trigger, alternative, persistence, and return value sufficiently; only the response shape beyond 'returns the spool' is unspecified, which is minor.

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 nine parameters already carry documented meanings and defaults; the description adds no additional syntax, units, or constraints beyond what the schema states, so the baseline 3 applies.

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 ('Record a new spool') plus scope ('user's local filament inventory'), which unambiguously separates it from creation of filament profiles and from update/list operations among the siblings.

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 an explicit trigger ('when the user buys or opens a spool') and names the overlapping alternative, create_filament_profile, but doesn't say when to prefer update_spool versus this tool after a purchase, leaving one small inference.

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