Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

List presets

list_presets
Read-onlyIdempotent

List printer, process, and filament preset names to find exact names for slicing, comparing slices, or reading settings; filter by search term or printer.

Instructions

List preset names so you can pass exact ones to slice_model, compare_slices or get_preset.

Use this to discover names; use get_preset to read the settings inside one preset. With a printer, only process and filament presets made for that printer are listed, the user's own presets first. Returns {count, presets: [{name, source}], truncated} with at most 300 rows. Read-only.

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": {
      "kind": "<kind>"
    },
    "name": "list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich presets: 'machine' (printers), 'process' (layer height, speeds) or 'filament'.
searchNoCase-insensitive part of the name to filter by, e.g. 'PETG' or '0.16mm'.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.
include_incompatibleNoAlso list process/filament presets made for other printers, marked fits_printer=false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • addedInput schema / properties / include_incompatible / description
      Added value: +"Also list process/filament presets made for other printers, marked fits_printer=false."
    • addedInput schema / properties / kind / description
      Added value: +"Which presets: 'machine' (printers), 'process' (layer height, speeds) or 'filament'."
    • addedInput schema / properties / printer / description
      Added value: +"Printer preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window."
    • addedInput schema / properties / search / description
      Added value: +"Case-insensitive part of the name to filter by, e.g. 'PETG' or '0.16mm'."
  2. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered and the closing "Read-only" is redundant. The description still adds real behavioral context the annotations cannot convey: printer-scoped filtering, user presets sorted first, and a hard 300-row truncation cap with a `truncated` flag.

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?

Purpose and downstream use are front-loaded, then behavior, then return shape — a clean progression with no filler. The only wasted clause is the trailing "Read-only," which duplicates the annotation set; everything else earns its place.

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?

There is no output schema, and the description compensates by spelling out the return shape ({count, presets: [{name, source}], truncated}) and the row cap. For a simple discovery tool with fully documented params, nothing an agent needs 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.

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all four parameters; baseline would be 3. The description goes beyond it by explaining the consequence of supplying `printer` (only process/filament presets made for that printer are listed), which clarifies filtering behavior rather than just restating field names.

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?

The first sentence gives a specific verb and resource (list preset names) and immediately ties the output to three concrete downstream consumers (slice_model, compare_slices, get_preset). That is enough for an agent to distinguish this from get_preset or save_user_preset without opening the schema.

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

Usage Guidelines5/5

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

It states the when-to-use case ("Use this to discover names") and names the alternative plus its distinct purpose ("use get_preset to read the settings inside one preset"). The printer-scoping note further tells the agent which subset of results to expect in that context.

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