Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Render plate image

render_plate
Read-only

Render a plate image to check model orientation and bed contact before slicing, or verify sliced toolpath support placement after slicing.

Instructions

Render a picture of the plate: the models before slicing (editor) or the toolpaths after it (preview).

view="editor": the models on the bed BEFORE slicing - use to check orientation, plate contact, and first-layer footprint (an Euler triple is near-unreadable; this is the ground truth). view="preview": the sliced toolpaths colored by feature role AFTER a successful slice - support is visibly distinct, so use it to check where support actually went. angle: iso|top|front|left|right|rear|bottom. frame: "plate" zooms out to the whole bed (where the part sits, footprint), "object" zooms in on the model/toolpaths (detail). Defaults to "plate" for the editor view and "object" for the preview view; pass it explicitly when a side view of a small part would otherwise be a speck on a big bed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoeditor
angleNoiso
frameNo
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.6/5.0
Behavior4/5

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

No contradiction with readOnlyHint=true — rendering an image is a pure read. The description adds behavior the annotation cannot: the preview view requires a successful slice as a precondition, and support geometry is visually distinguished by feature-role coloring. It stops short of saying what the call returns (inline image content vs. a path), which is the one behavioral gap.

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?

Front-loaded one-line summary, then per-parameter paragraphs keyed to the exact argument names. Every clause carries information — even the parenthetical about Euler triples earns its place by justifying why to prefer a render over numeric pose data.

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?

Five optional parameters, no output schema, and zero schema coverage: the description compensates for almost all of it by covering view, angle, and frame with defaults and intent. The remaining shortfall is that it never characterizes the returned image (resolution relationship to width/height, format), which an agent would need to reason about the result.

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 description coverage is 0% and no parameter carries an enum, so the description is doing real work: it enumerates the seven angle values (iso|top|front|left|right|rear|bottom), defines the plate-vs-object semantics of frame, and states both per-view defaults. Only width and height go undocumented, a minor omission since their meaning is self-evident.

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 ('Render a picture of the plate') and immediately splits the resource into its two distinct modes, editor (pre-sliced models) and preview (sliced toolpaths). That framing makes it distinguishable from slice, describe_plate, and the other plate siblings without opening a 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 conditions for each view: editor for orientation, plate contact, and first-layer footprint; preview only after a successful slice to verify where support landed. It also says when to override the frame default (a side view of a small part on a large bed), which is genuine decision guidance rather than description.

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