Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Model info

model_info
Read-onlyIdempotent

Measure a 3D model before slicing to check its size, volume, surface area, triangle count, separate pieces, watertightness, and build-volume fit.

Instructions

Measure a 3D model before slicing: size, volume, surface area, triangles, separate pieces, watertightness and whether it fits the printer's build volume.

Use it first on an unfamiliar file. For which way up to print it use find_best_orientation, and to test a rotation or scale against the bed use check_bed_fit. STEP files are converted with the slicer first. Read-only; it never changes the file.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / path / description
      Added value: +"Path to an STL, OBJ, 3MF or STEP file on this computer."
    • addedInput schema / properties / printer
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Printer preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.",
      +  "title": "Printer"
      +}
  2. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds real context beyond that by noting STEP files are converted with the slicer first, which signals an implicit conversion step. The closing read-only sentence largely restates the annotations, which is why this is not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core measurement capability, followed by routing guidance and the read-only caveat. No filler or repeated phrasing.

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?

There is no output schema, so the description correctly enumerates the measurements returned, and it covers the non-obvious STEP conversion behavior. For a two-parameter read-only inspection tool, nothing an agent needs is missing.

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 both parameters (path, printer) are fully documented in the schema, so the baseline is 3. The description only indirectly ties the printer parameter to build-volume fit, adding no format or selection detail beyond what the schema already says.

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 specific verb and resource ("Measure a 3D model") plus the exact metrics returned: size, volume, surface area, triangles, separate pieces, watertightness and bed fit. An agent can distinguish this inspection tool from slicing or orientation tools 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 explicit when-to-use ("Use it first on an unfamiliar file") and names two alternatives with the conditions that select them: find_best_orientation for orientation, check_bed_fit for testing a rotation or scale against the bed.

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