Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Analyze strength

analyze_strength
Read-onlyIdempotent

Recommends print orientation and slicer settings for load-specific part strength, flags thin waists, and returns overrides plus rotation for slicing.

Instructions

Recommend an orientation and slicer settings (walls, top/bottom layers, infill, layer height) that make a part strong for how it will be used.

Use it when the user says a part must hold, bend or survive impact; find_best_orientation only ranks orientations. Also flags thin waists in the shape. Returns overrides and a rotation to pass to slice_model, with reasons; check the cost with compare_slices. 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": {
      "model": "<model>"
    },
    "name": "analyze_strength"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadNoHow the part is loaded: 'general', 'tension', 'compression', 'bending', 'impact' or 'torsion'.general
modelYesPath to an STL, OBJ, 3MF or STEP file on this computer.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.
filamentNoFilament preset, used for material-specific advice. Default: the selected filament.
priorityNo'max_strength', 'balanced' or 'light' (less filament).balanced
load_axisNoDirection of the load in model coordinates: 'x', 'y', 'z' or [x, y, z]. For a gear pushed at its teeth, use an axis in the gear's plane.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.3/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, and the description's closing 'Read-only' largely restates that. What it adds beyond the annotations is substantive: it discloses the return payload (overrides plus a rotation), that reasons are attached, and that it inspects geometry for thin waists. It does not discuss runtime or failure modes on unreadable models, which keeps 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?

It is front-loaded with purpose, then usage and sibling routing, then return value — a sensible order with no filler sentences. The trailing 'Read-only' is redundant against the annotations and is the one line that does not earn its place.

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 six parameters and no output schema, the description correctly compensates by describing what comes back (overrides, rotation, reasons) and where that output flows next. What is missing is any indication of how the overrides are shaped or applied, so an agent knows they are not silently written but handed to slice_model — that is implied by 'to pass to slice_model' rather than stated.

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 the schema already explains load, model, printer, filament, priority and load_axis including examples. The description adds no parameter-level meaning beyond the phrase 'for how it will be used', which only loosely gestures at the load parameter. Baseline 3 is appropriate when the schema does all the work.

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 opens with a specific verb-plus-resource: recommend an orientation and slicer settings (walls, top/bottom layers, infill, layer height) for strength. It explicitly distinguishes itself from find_best_orientation by noting that tool 'only ranks orientations', and it adds a secondary capability (flagging thin waists). An agent can place this tool without opening any 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?

It gives a concrete trigger ('when the user says a part must hold, bend or survive impact'), names the nearest alternative and why it is insufficient, and points forward in the workflow to slice_model and compare_slices for cost. The only minor omission is that it does not say when NOT to use it (e.g. purely cosmetic parts), but the positive routing is precise.

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