Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Read a preset's settings

get_preset
Read-onlyIdempotent

Reads a preset's merged settings so you can find exact setting keys and values to use as overrides for slicing, comparison, or saving.

Instructions

Read the effective settings of one preset, with its inheritance chain merged.

Use it to find the exact setting names to pass as overrides to slice_model, compare_slices or save_user_preset (search='infill' finds sparse_infill_density and friends). Values longer than 200 characters are elided unless you ask for them by keys. Returns {preset, source, inherits, settings}. 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": {
      "name": "<name>",
      "kind": "<kind>"
    },
    "name": "get_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNoExact setting keys to return in full, including long G-code templates.
kindYes'machine', 'process' or 'filament'.
nameYesPreset name, or a unique part of it, e.g. 'Anycubic PLA'.
searchNoOnly return settings whose key contains this text, e.g. 'infill', 'support', 'temp', 'retract'.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.1
    • addedInput schema / properties / keys / description
      Added value: +"Exact setting keys to return in full, including long G-code templates."
    • addedInput schema / properties / kind / description
      Added value: +"'machine', 'process' or 'filament'."
    • addedInput schema / properties / name / description
      Added value: +"Preset name, or a unique part of it, e.g. 'Anycubic PLA'."
    • 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: +"Only return settings whose key contains this text, e.g. 'infill', 'support', 'temp', 'retract'."
  2. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds behavior that annotations cannot convey: inheritance merging, the 200-character elision rule and how to defeat it with keys, and the exact return shape {preset, source, inherits, settings}. That is substantial added context for a read tool.

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?

Four tight sentences, front-loaded with purpose, then usage, then behavior, then return shape. Every sentence carries information an agent needs, with no filler.

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 five-parameter read tool with no output schema, the description supplies return structure, the truncation rule, and the inheritance behavior, and the 100%-covered schema handles the parameters. It could still say what happens when name or printer matches multiple presets, which matters for a lookup that accepts partial names.

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 coverage is 100%, so the schema already documents every parameter, including keys, search, kind and printer; the baseline is therefore 3. The description adds real value by explaining how keys interacts with elision and by showing what search matches, but it does not explain kind or printer semantics beyond what the schema says.

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 (read a preset's effective settings) plus a key scope detail: the inheritance chain is merged into the result. An agent can distinguish this from list_presets 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 Guidelines4/5

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

Gives explicit when-to-use guidance: it names the downstream consumers (slice_model, compare_slices, save_user_preset) and describes a concrete workflow (search='infill' to discover sparse_infill_density). It lacks explicit when-not conditions or a pointer to list_presets for enumeration, so it falls short of full routing guidance.

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