Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Diagnose a failed print

diagnose_print
Read-onlyIdempotent

Identify 3D print defects from photos and get targeted setting adjustments to fix failed prints. Read-only; no presets changed.

Instructions

Explain what went wrong with a failed 3D print and which settings to change, from defects you identify in the user's photos.

First call it with no issues to get the defect catalogue, compare the photos with each 'looks_like', then call again with the matching ids. Suggestions are computed from the presets actually in use; fixes that conflict are reported, not applied. Read-only: it changes no presets (save them with save_user_preset if the user wants to keep them). Returns causes, checks and an overrides dict for slice_model.

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

Input Schema

NameRequiredDescriptionDefault
issuesNoDefect ids seen in the photos, e.g. ['stringing', 'warping']. Omit to get the catalogue of 13 defects with what each looks like.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.
processNoProcess preset (layer height, speeds), e.g. '0.20mm Standard'. Omit to use the slicer window's selection.
filamentNoFilament preset the print used. Default: the selected filament.
severityNo'mild', 'moderate' or 'severe'; scales how big the suggested changes are.moderate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well past that: suggestions are computed from the presets actually in use, conflicting fixes are surfaced rather than applied, and the return payload is spelled out (causes, checks, an overrides dict for slice_model). That is genuinely useful behavioral context an agent could not get from the annotations alone.

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 paragraphs with no filler: purpose first, then the two-call protocol, then the mutation boundary and return shape. The procedural instruction is front-loaded where the agent will act on it.

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 return-value burden and does so by naming causes, checks, and an overrides dict destined for slice_model. Combined with the two-phase call protocol and the read-only boundary, an agent has everything needed to call it correctly on the first try.

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 description coverage is 100%, so every one of the five parameters — including the null-omission default for issues, printer, process and filament, and the mild/moderate/severe enum on severity — is already documented in structured data. The description reinforces the no-issues catalogue behavior but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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?

It states a specific verb and resource ('Explain what went wrong with a failed 3D print and which settings to change') and scopes the input source ('from defects you identify in the user's photos'). It also distinguishes itself from siblings by naming save_user_preset and slice_model as the places where presets are persisted and the overrides are consumed.

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 prescribes the exact operating procedure: call with no issues to get the defect catalogue, compare photos against each 'looks_like', then call again with matching ids. It also states an exclusion — conflict fixes are reported, not applied — and routes persistence to save_user_preset, so the agent knows both when to use this and when to reach for a sibling.

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