Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get CANVAS slots

get_printer_slots
Read-only

Reads the filament trays of an Elegoo Centauri Carbon 2 with a CANVAS unit, reporting the active tray plus each tray’s label, status, material, brand, and colour for slot mapping.

Instructions

Read the filament trays of an Elegoo Centauri Carbon 2 with a CANVAS unit; only for that printer, and slow (up to about 18 s).

It reports which tray is active, and for each tray its label (A1, A2, ...), status, material, brand and colour. Read-only; needs fork v2.4.2-mcp.14 or later. OrcaSlicer's API serves one request at a time while the printer is asked, so other tools wait.

Per tray: status is loaded, preloaded (filament waiting at the feeder, not yet pulled in), disconnected or error. ready is true when the tray can be printed from now. unknown_filament is true when the tray reports no filament type or name. Use canvas_id and tray_id from here in set_filament_slot_mapping.

When the printer is not supported or not reachable the reply is supported false with a reason (not_elegoo_cc2, no_canvas, unreachable, too_many_clients, registration_refused, timeout, printer_error, firmware_too_old) and a message. Relay the message to the user.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.19

TDQS

A4.6/5.0
Behavior5/5

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

Annotations supply only readOnlyHint, and the description goes well beyond it: an up-to-18-second duration, the fact that OrcaSlicer serializes requests so other tools block, a minimum fork version, and an enumerated set of failure reasons. It also defines the per-tray semantics (status values, ready, unknown_filament) that determine how results should be read.

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-loads the decisive constraints (device scope, slowness) in the first line, then layers semantics and error handling. It is dense but every block earns its place; the status enumeration could be tighter if an output schema existed.

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 carries the full burden and does so: it names every returned field family, defines the status values and boolean flags, and lists all error reasons with the instruction to relay the message. Nothing needed to call it or interpret the result 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?

The tool takes no parameters, so there is no input semantics to explain; baseline credit applies. The description instead documents returned identifiers (canvas_id, tray_id) and their downstream use, which adds meaning even though it lives on the output side.

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 ("Read the filament trays") and immediately narrows scope to an Elegoo Centauri Carbon 2 with a CANVAS unit, which no sibling tool covers. An agent can tell this apart from get_printer_status or get_filament_slot_mapping 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 Guidelines4/5

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

Gives a hard eligibility rule ("only for that printer") and practical guidance about latency and serialization, plus names set_filament_slot_mapping as the consumer of the returned ids. It stops short of explicitly routing the agent elsewhere when the printer is unsupported, relying on the listed error codes instead.

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