Skip to main content
Glama
orcaslicer-mcp

orcaslicer-mcp

Transform object

transform_object

Move, rotate, or scale a single OrcaSlicer object by ID using relative translation/rotation or absolute scaling; use plate tools to reposition it across plates or tidy a whole plate.

Instructions

Move, rotate or scale one object by id; use move_object_to_plate to change its plate, or arrange_plate to tidy the whole plate.

translate=[dx,dy,dz] mm (relative), rotate=[rx,ry,rz] degrees (relative), scale=[sx,sy,sz] absolute factor. Provide at least one.

On fork v2.4.2-mcp.13 and later the object then belongs to whichever plate it sits on, as after a drag in the window; list_objects shows the plate. To send an object to another plate, move_object_to_plate is simpler than working out coordinates.

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": {
      "object_id": "<object_id>"
    },
    "name": "transform_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
rotateNo
object_idYes
translateNo

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?

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries the rest and delivers: relative vs absolute semantics per field, and the v2.4.2-mcp.13+ behavior that the object takes on the plate it sits on, with list_objects as the way to observe it. It stops short of stating whether transforms are undoable or what the call returns, which is a modest gap for a mutation tool.

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?

Guidance about alternatives is front-loaded in sentence one, with parameter semantics immediately after and version-specific behavior last. The fork-version paragraph is slightly long, but it carries real behavioral information rather than filler.

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?

For a 4-parameter mutation tool with no output schema and thin annotations, the description covers units, relativity, alternative routing, and a version-dependent side effect. What remains unstated is the response shape and whether the transform is reversible, but no return contract was promised.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: object_id is the target, translate is [dx,dy,dz] in millimetres and relative, rotate is [rx,ry,rz] in degrees and relative, and scale is an absolute [sx,sy,sz] factor. Units, relative/absolute semantics, and the 'at least one' constraint are all supplied beyond the bare field names.

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?

The description opens with a specific verb triad plus resource and scope: "Move, rotate or scale one object by id." It immediately distinguishes itself from move_object_to_plate (plate changes) and arrange_plate (whole-plate tidying), so an agent can select it without opening the 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?

It names two concrete alternatives with the exact conditions that select them: use move_object_to_plate to change an object's plate, and arrange_plate to tidy an entire plate. It also states 'Provide at least one' transform, which is real usage guidance about valid invocation.

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