Skip to main content
Glama
creator5-slicer-mcp

creator5-slicer-mcp

by rsutcliffe

open_in_slicer

Opens a sliced .3mf project in the slicer window with chosen settings applied, so you can review the model and use the slicer's Slice and Print buttons. Pass the project path returned by slice_model.

Instructions

Open a project in the slicer's window, ready to slice and print.

Pass the project_3mf path returned by slice_model. The slicer shows the model with all the chosen settings applied, and its own Slice and Print buttons work as usual. A .gcode file opens as a view-only preview that cannot be printed.

Args: path: Absolute path to the .3mf project (preferred), or a .gcode or model 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": "open_in_slicer"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses that the slicer applies the chosen settings, that its Slice and Print buttons remain functional, and critically that a .gcode opens as a view-only preview that cannot be printed. It does not say whether the call blocks, launches a GUI, or what it returns on failure.

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?

Front-loaded with the purpose, then the usage note, then the format caveat, then an args block. The only waste is slight redundancy between "ready to slice and print" and "its own Slice and Print buttons work as usual."

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?

For a single-parameter tool with no annotations and no output schema, the description covers purpose, sourcing of the input, accepted formats, and one important behavioral limitation. It stops short of describing failure modes or post-open state, which would be the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (a bare string 'path'), so the description must compensate, and it does: the path must be absolute, .3mf is preferred, and .gcode or model files are also accepted. It leaves open what happens with a relative or nonexistent path.

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?

States a specific verb and resource (open a project in the slicer's window) plus the end goal (ready to slice and print). It partly disambiguates from slice_model by explicitly consuming slice_model's output, though it never says outright what this tool is not for.

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?

"Pass the project_3mf path returned by slice_model" gives concrete sequencing guidance for the primary case, and the .gcode sentence establishes a second, degraded case. Missing an explicit statement of when not to call it (e.g. before slicing/settings exist).

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