Skip to main content
Glama
Sign In
OrcaSlicer-mcp

OrcaSlicer-mcp

by BeMuCa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

slice_model

Slices STL/3MF models into G-code with time and material estimates, supporting process and filament overrides, bed type selection, and custom output paths.

Instructions

Slice an STL/3MF and return G-code path plus time/material estimates. overrides are process settings by OrcaSlicer key, e.g. {"sparse_infill_density": "40%", "wall_loops": "4", "enable_support": "1"}; filament_overrides likewise for the filament, e.g. {"nozzle_temperature": "215"}. Use get_profile to see every key and its current value. bed_type picks the plate temperatures: "Textured PEI Plate", "Hot Plate" (smooth PEI), "Cool Plate", "Engineering Plate". output_dir defaults to /sliced/-.

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_path": "<model_path>",
      "vendor": "<vendor>",
      "machine": "<machine>",
      "process": "<process>",
      "filament": "<filament>"
    },
    "name": "slice_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYes
machineYes
processYes
bed_typeNoTextured PEI Plate
filamentYes
overridesNo
model_pathYes
output_dirNo
filament_overridesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden itself and does add meaningful behavior: it returns a G-code path plus time/material estimates, explains override map formats, lists bed_type choices, and gives the output_dir default. It still omits operational details such as whether files are written or overwritten, runtime expectations, error behavior, and permission or installation prerequisites.

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?

The description is front-loaded with the core purpose and then moves efficiently through the parameters that most need clarification. The examples for overrides and bed types are compact and earn their place, with no obvious filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 9-parameter slicing tool with no annotations and no output schema, the description covers return values and the trickiest override parameters reasonably well. It remains incomplete on required profile-selection parameters and operational side effects, so an agent would still need significant inference or external lookup to invoke it confidently.

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 0%, so the description must compensate for all parameters. It does well for overrides, filament_overrides, bed_type, and output_dir by giving formats, examples, accepted values, and defaults, but it leaves the required vendor, machine, process, filament, and model_path parameters largely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb and resource: slice an STL/3MF and return a G-code path plus time/material estimates. It names get_profile as a helper for override keys, but it does not explicitly distinguish this action from related siblings such as gcode_stats or list_profiles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a useful instruction to use get_profile to inspect override keys and current values, which implies the correct workflow for overrides. However, it does not say when to choose slice_model versus sibling tools or list prerequisites such as needing an installed slicer and valid profile names.

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

Deploy Server

Other Tools