PrusaSlicer-MCP

by JorgeAlbareda

Overview Schema Source Related Servers Discussions Admin

Python

Local

preview_layer

Display a specified layer in the live PrusaSlicer preview to inspect slicing results and print details at that layer.

Instructions

Show a given layer in the live preview (GUI engine, v2).

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": {
      "layer": "<layer>"
    },
    "name": "preview_layer"
  }
}

Input Schema

Name	Required	Description	Default
`layer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must carry full behavioral disclosure. It reveals that this is a GUI engine v2 live-preview operation, which is useful context, but it omits whether the GUI must be running, whether the action is reversible, what happens with an invalid layer index, or any side effects on the current view.

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?

A single, front-loaded sentence with no wasted words. It immediately states the action and the operational context.

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

Completeness2/5

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

For a GUI-control tool with no annotations, no output schema, and no schema descriptions, the definition is too sparse. It lacks the layer indexing convention and runtime prerequisites an agent would need to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0% for the single layer parameter, so the description must compensate. It only repeats that a 'given layer' is shown, adding no index base, valid range, or meaning beyond the schema's own parameter name.

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 states a specific verb (Show) and resource (a given layer) in a precise context (live preview, GUI engine v2). It is clear what the tool does, but it does not distinguish itself from the sibling show_in_slicer or other preview tools.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no comparison to alternatives such as show_in_slicer. The description only implies usage through its purpose statement.

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