Skip to main content
Glama
Anycubic Slicer MCP

Anycubic Slicer MCP

Check bed fit

check_bed_fit
Read-onlyIdempotent

Checks whether an STL, OBJ, 3MF or STEP model fits a printer's build volume, with optional rotation or scale tests, and suggests turning, scaling, laying flat, or splitting in CAD when it doesn't.

Instructions

Check whether a model fits the printer's build volume, optionally after a rotation or scale.

If it doesn't fit it suggests a 45-degree turn, a scale percentage, laying it down, or splitting it in CAD. model_info gives the same fit check without trying transforms. 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": "check_bed_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesPath to an STL, OBJ, 3MF or STEP file on this computer.
scaleNoScale factor to test first, e.g. 0.8.
printerNoPrinter preset name or a unique part of it, e.g. 'Kobra X'. Omit to use the printer selected in the slicer window.
rotation_degNoRotation to test first, e.g. {'z': 45}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive, so 'Read-only' in the description is largely redundant. The description does add real behavioral value by disclosing the outcome on failure (suggests a 45-degree turn, a scale percentage, laying it down, or splitting in CAD), though it leaves ambiguous whether the tested transform is persisted or purely hypothetical.

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?

Three short sentences with the purpose front-loaded and the sibling comparison immediately after; nothing is buried. The standalone 'Read-only.' sentence repeats an annotation and is the one piece of low-value text.

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 no output schema, the description usefully sketches what the result contains (fit verdict plus actionable remediation suggestions). What remains thin is whether a passing check reports headroom or which axis is tight, but for a straightforward read-only validation tool this is close to sufficient.

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%, so all four parameters are already documented including examples like 0.8 and {'z': 45}. The description only restates that the transform is optional, adding no new meaning beyond the schema's own parameter notes, which fits the baseline-3 case.

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 ('Check whether a model fits the printer's build volume') plus the optional transform scope. It explicitly positions itself against the sibling model_info, so an agent can separate the two without opening either schema.

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?

Names the alternative ('model_info gives the same fit check without trying transforms'), which clearly implies this tool is the one to pick when a rotation or scale must be tested. It stops short of an explicit 'use this when / don't use this when' statement, so the routing condition must be inferred from the contrast.

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