Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Slicer status

slicer_status
Read-onlyIdempotent

Checks whether Anycubic Slicer Next is installed and reports selected printer, process, filaments, plate type, presets, and build volume; use before slicing or when a slice fails with “not found.”

Instructions

Report whether Anycubic Slicer Next is installed and what its window currently has selected.

Call this first in a session, and whenever a slice fails with "not found": it returns the server version, operating system, slicer executable and version, data folder, how many printer/process/filament presets exist, the selected printer, process, filaments and plate type, and the build volume. Read-only; it only reads the slicer's config files and starts nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/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 the safety profile is partly structured. The description still adds value beyond that by scoping the mechanism ('it only reads the slicer's config files and starts nothing'), which rules out launching the slicer as a side effect. It doesn't cover failure modes such as what is returned when the slicer is absent, keeping it below a 5.

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?

The purpose and the 'call this first' instruction are front-loaded, and the payload list is dense but each item is concrete. The enumerated return fields run long in a single sentence but no sentence is filler.

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 carries the burden of describing returns and does so exhaustively: environment details, preset counts, current selections and build volume. For a zero-parameter, read-only status tool, an agent has everything needed to decide to call it and to interpret the result.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter discussion, and instead spends its words on the return payload, which is the useful information here.

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 description names a specific verb and resource: it reports whether Anycubic Slicer Next is installed and what its window has selected. It then enumerates the exact state read (server version, OS, executable, data folder, preset counts, selected printer/process/filaments/plate, build volume), which makes it unmistakable against siblings like get_preset or list_presets.

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?

It gives explicit invocation triggers: 'Call this first in a session' and 'whenever a slice fails with not found'. That is stronger than implied usage. It stops short of naming an alternative tool to use instead when the check passes, so it doesn't reach the full when/when-not/alternatives bar.

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