Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List plate objects

list_objects
Read-only

Lists all objects in the current OrcaSlicer project with their IDs, names, sizes, placement, and plate so object-specific tools can use those IDs.

Instructions

List the objects in the project with their ids, names, sizes, placement and plate; the object tools take these ids.

Each has a stable id, name, size_mm, transform (offset/rotation/scale) and, on fork v2.4.2-mcp.13 and later, the 0-based plate it sits on (-1 when it is off every plate).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true), so the description correctly spends its words on behavior instead: the exact per-object attributes, 0-based plate indexing, the -1 sentinel for unplated objects, and a version gate (fork v2.4.2-mcp.13+). Ordering of results, empty-project behavior, and cost/pagination are not mentioned.

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?

Two sentences, front-loaded with purpose and return fields, then the plate-index detail. Every clause earns its place; the only blemish is an awkward line wrap inside the version string, which does not hurt comprehension.

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?

With no parameters and no output schema, the description must carry the return-value burden, and it does — naming each field plus the plate sentinel and version condition. Minor gaps remain around result ordering and what an empty project yields.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description sensibly redirects effort to output shape rather than inventing parameter context.

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?

States a specific verb and resource ("List the objects in the project") and enumerates exactly what comes back: ids, names, sizes, placement, plate. It also signals the downstream relation to the object tools. It does not name list_plates explicitly, so the distinction from sibling list tools is only implied.

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

Usage Guidelines3/5

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

The clause "the object tools take these ids" implies this is the discovery step before any object-mutating call, which is real usage context. There is no explicit when-not guidance or named alternative, and no note about calling it before/after plate or project changes.

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