Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete plate (its objects are parked off-plate)

delete_plate
Destructive

Remove a plate from the OrcaSlicer project while parking its objects beside the bed instead of deleting them; the only remaining plate cannot be removed.

Instructions

Delete a plate; the objects on it are parked beside the bed, not deleted.

OrcaSlicer parks them as the toolbar's delete does, and the reply says how many were moved off-plate (objects_moved_off_plate). Use move_object_to_plate to put them somewhere printable. OrcaSlicer parks them where the next plate appears, so an add_plate straight after a delete picks them back up.

The only plate cannot be deleted (422 last_plate). Call list_plates first for the index; this cannot be undone through the API.

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": {
      "index": "<index>"
    },
    "name": "delete_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes0-based plate index from list_plates. Later plates shift down one index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.17

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description justifies and refines that by explaining objects survive as parked and reporting the objects_moved_off_plate count. It also discloses the 422 error code and that the action is irreversible through the API. Slightly short of 5 only because it never clarifies whether the deleted plate's settings/config are recoverable.

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?

Well front-loaded: the surprise (objects are parked, not destroyed) leads, then recovery paths, then failure modes. Three short paragraphs are justified by the amount of non-obvious behavior conveyed, though the second mention of OrcaSlicer's parking behavior is slightly repetitive.

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?

No output schema exists, yet the description names the return field (objects_moved_off_plate), the error code, the precondition, and the recovery tools. Nothing needed to call it correctly is missing.

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 100% and already documents index as a 0-based value from list_plates with downstream shifting. The description reinforces that routing and implies the index is positional state rather than a stable id, adding mild but real meaning.

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 ('Delete a plate') and immediately adds the defining scope qualifier: the objects on it are parked, not deleted. That distinction is exactly what separates it from delete_object and from a naive destructive delete.

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 preconditions ('call list_plates first for the index'), the failure case ('the only plate cannot be deleted (422 last_plate)'), and routes follow-up work to move_object_to_plate. It even covers the sequencing alternative: add_plate right after a delete picks the parked objects back up.

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