Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Open in slicer

open_in_slicer

Opens a model, G-code, or 3MF file in the Anycubic Slicer Next window when you need to see or edit it, and refuses 3MF files containing post-processing scripts.

Instructions

Open a file in the Anycubic Slicer Next window on the user's screen.

Only call it when the user asks to see or edit something in the slicer; every other tool works without the window. 3MF files are checked for post-processing scripts first and refused if they have one. Changes no files.

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": {
      "path": "<path>"
    },
    "name": "open_in_slicer"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesA model (STL, OBJ, 3MF, STEP), a .gcode or a .gcode.3mf on this computer.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / path / description
      Added value: +"A model (STL, OBJ, 3MF, STEP), a .gcode or a .gcode.3mf on this computer."
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: 3MF files are inspected for post-processing scripts and refused if present, and the call makes no file changes. Safety and side-effect profile are covered well. It does not say what happens if the slicer window/app is not already running, which is the one gap an agent could hit.

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 core action, then the usage constraint, then the safety caveat. Every sentence carries distinct information and nothing is repeated.

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?

With an output schema present, return values need no explanation, and the description covers action, trigger, and refusal condition. Only the precondition of a running slicer window is unaddressed, a minor gap for a GUI-launching tool.

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% and the single path parameter already enumerates accepted formats (STL, OBJ, 3MF, STEP, .gcode, .gcode.3mf), so the description adds essentially nothing about syntax. Its only extra signal is that 3MF inputs get the script check, which is behavior rather than parameter meaning.

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 concrete verb+resource (open a file in the Anycubic Slicer Next window on the user's screen) and explicitly separates itself from all siblings by noting that every other tool works without the window, so the agent can tell when this one is unique.

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 an explicit trigger ('only call it when the user asks to see or edit something in the slicer') and an implicit exclusion (all other work should use the other tools). Nothing is left to inference about when this tool is the right choice.

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