Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

List spools

list_spools
Read-onlyIdempotent

List local filament spools and their remaining amounts. Use before a long print to pick a spool with enough material, optionally filtered by material or required grams.

Instructions

List the spools in the local inventory with how much filament each has left.

Use it before a long print to pick a spool with enough filament. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_spools"
  }
}

Input Schema

NameRequiredDescriptionDefault
need_gNoGrams a planned print needs; spools with enough left (plus 5%) are marked.
materialNoOnly list spools of this material.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the closing 'Read-only' sentence is redundant. The description does add one genuine behavioral detail - that spools meeting a need are marked - but says nothing about result size, ordering, or how the local inventory is scoped.

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?

Three short sentences, front-loaded with the resource and payload, then usage, then safety. The only wasted sentence is 'Read-only', which merely restates the annotations.

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 two-optional-parameter list tool with no output schema, the description covers what is returned ('how much filament each has left') and when to reach for it. Missing only minor operational detail such as ordering or result limits.

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%, and the schema itself already explains need_g (including the '+5%' buffer) and material. The description adds no syntax, units, or defaulting information beyond what the schema provides, so the baseline 3 applies.

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 ('List the spools in the local inventory') plus the payload ('how much filament each has left'), which clearly separates it from mutation siblings like add_spool and update_spool. It does not explicitly name a sibling, so it lands just below the top of the scale.

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 a concrete usage context: 'Use it before a long print to pick a spool with enough filament.' That is clear when-to-use guidance tied to a real workflow, but there are no exclusions or pointers to alternative tools for related questions.

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