Skip to main content
Glama
orcaslicer-mcp

orcaslicer-mcp

Add plate

add_plate

Add an empty build plate so parts can print separately, returning its 0-based index for moving objects and selecting plates. Fails while slicing or at the plate limit.

Instructions

Add an empty plate, like the toolbar's Add plate button, so parts can print separately.

Returns the new plate's 0-based index for move_object_to_plate and select_plate.

Use it when parts should print separately: load them, add a plate, move the second part across with move_object_to_plate, then select_plate and slice each one. A plate cannot be added while a slice is running (409) or at the build's plate limit (422). On OrcaSlicer 2.5, the 2nd, 5th and 10th plates widen the plate grid, which clears every plate's slice result, as the toolbar button does: slice again afterwards.

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": "add_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectNoMake the new plate the current one, as the toolbar button does. Pass false to keep working on the plate that is current now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.17

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say the tool mutates and is non-destructive; the description adds real value beyond that by disclosing the returned 0-based index, the two error codes and their causes, and the OrcaSlicer 2.5 side effect where adding the 2nd, 5th or 10th plate clears every plate's slice result. The only gap is that it doesn't state whether the returned index shifts after plates are deleted.

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 core action and return value before the workflow and caveats, and every sentence carries information. The repeated "like the toolbar's Add plate button" phrasing is mild redundancy that could be trimmed.

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

Completeness5/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 supplies the return value (0-based plate index) and the failure modes, plus the version-specific side effect, so an agent has everything needed to call and interpret the result. Nothing material is missing for a one-parameter mutation tool.

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?

The single parameter has 100% schema description coverage that already explains select=true/false behavior, so the schema carries the semantics. The description adds only indirect context (that the new plate becomes current, matching the toolbar button) rather than new meaning for the parameter itself, so the baseline 3 applies.

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+resource ("Add an empty plate") and immediately clarifies the effect ("so parts can print separately"), which distinguishes it from move_object_to_plate, select_plate and the other plate siblings. It also names the analogous UI action, removing ambiguity about what 'plate' means here.

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 an explicit multi-step workflow (load parts, add plate, move_object_to_plate, select_plate, slice) that tells the agent exactly when this tool belongs in a sequence. It also states when the call will fail: 409 while a slice is running and 422 at the build's plate limit.

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