Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Create filament profile

create_filament_profile
DestructiveIdempotent

Creates a filament preset from spool-label details, fills missing values with material defaults, and previews before saving to the slicer's user presets.

Instructions

Turn the details printed on a filament spool label into a filament preset for the slicer.

Read the label photo yourself and pass what it says; only material is required, and anything missing gets a typical value for that material (listed in the result). The preset inherits from the closest existing preset for the printer. With save=false it only returns a preview; show it to the user, then call again with save=true to write it to the slicer's user presets (overwrite=true replaces an existing one). For other preset edits use save_user_preset.

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": "create_filament_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPreset name. Default: 'Brand Product Colour @printer'.
saveNoFalse (default) only previews. True writes the preset; do it after the user confirms the preview.
brandNoBrand on the label.
priceNoPrice paid for the spool, used to set cost per kg.
dryingNoDrying instructions from the label, kept in the profile notes.
bed_maxNoHighest bed temperature on the label, °C.
bed_minNoLowest bed temperature on the label, °C.
densityNoDensity in g/cm³ if printed on the label.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.
productNoProduct line on the label, e.g. 'Silk' or 'Matte'.
materialYesMaterial printed on the label, e.g. 'PLA', 'PETG', 'PLA+', 'ABS', 'TPU', 'PA-CF'.
weight_gNoNet filament weight in grams, e.g. 1000.
overwriteNoWith save=true, replace an existing preset of the same name.
colour_hexNoColour as '#RRGGBB', estimated from the photo if the label has none.
nozzle_maxNoHighest nozzle temperature on the label, °C.
nozzle_minNoLowest nozzle temperature on the label, °C.
colour_nameNoColour name on the label, e.g. 'Galaxy Black'.
diameter_mmNoFilament diameter, usually 1.75.
max_speed_mm_sNoMaximum print speed in mm/s if printed on the label.
add_to_inventoryNoWith save=true, also record the spool in the local inventory.
nozzle_recommendedNoRecommended nozzle temperature if the label gives one, °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds real behavior beyond that—auto-filled defaults listed in the result, inheritance from the closest existing printer preset, preview-then-write sequencing, and optional inventory recording. It does not spell out what happens to an unrelated preset when overwrite collides, a minor remaining gap.

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?

Roughly 85 words for a 21-parameter tool, front-loaded with the purpose, then required-vs-optional behavior, then the save/overwrite flow, then the sibling pointer. No sentence is redundant.

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?

With no output schema, the description still tells the agent that derived values appear in the result and that save=false yields a preview. Combined with the 100%-covered schema and annotations, an agent has everything needed to call this correctly.

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 baseline is 3; the description still adds cross-parameter meaning the schema lacks—only material is mandatory, omitted fields are derived from the material, and the printer defaults to the slicer's selected printer via inheritance. The rest of the 21 parameters are left to their schema descriptions.

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?

Names a specific transformation (spool-label details → slicer filament preset) and its resource, and explicitly contrasts itself with save_user_preset for other preset edits. An agent can distinguish it from siblings 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?

Gives the full workflow: read the label photo yourself, only material is required, missing fields get material-typical values, preview with save=false then re-call with save=true after user confirmation, and overwrite=true for replacement. It also routes non-creation preset edits to save_user_preset.

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