Skip to main content
Glama

Transform

transform
Destructive

Move or rotate an existing object in place without creating a new handle, using relative or absolute translation and rotation instead of editing Placement via set_property.

Instructions

Move and/or rotate an object in place (no new handle) — use instead of editing Placement via set_property.

translate: [x, y, z] mm. rotate_axis: [x, y, z], any length (default Z); angle: DEGREES about it, around the object's local origin. relative: True composes onto the current placement; False sets it absolutely.

Returns {handle, name, placement: {base [x,y,z] mm, axis, angle_deg}}.

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": {
      "handle": "<handle>"
    },
    "name": "transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNo
handleYes
relativeNo
translateNo
workspaceNoRun this call in this named workspace
rotate_axisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety bar is lower, and the description adds genuine context beyond them: mutation happens in place without producing a new handle, rotation is about the object's local origin, angles are in degrees, and relative composes onto the current placement. It does not mention transaction requirements or whether the prior placement is recoverable, which matters for a destructiveHint tool.

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?

The differentiator and the exclusion are front-loaded in the first sentence, followed by compact per-parameter lines and a one-line return shape. No sentence is filler and each line adds a fact not present in the schema.

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 output schema, the description correctly supplies the return shape ({handle, name, placement}), plus defaults and units. The remaining gap is operational: it never says whether this must run inside transaction_open/transaction_commit, which is relevant given destructiveHint=true and the presence of transaction siblings.

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 description coverage is only 17% (just workspace), so the description carries the load — and it does: units (mm) and shape for translate, 'any length (default Z)' for rotate_axis, DEGREES and the pivot for angle, and compose-vs-absolute for relative. That compensates for nearly every undocumented parameter.

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 pair and resource ('Move and/or rotate an object in place (no new handle)') and immediately distinguishes itself from the sibling set_property by declaring it is the preferred path for placement changes. The parenthetical '(no new handle)' pins down the mutation-in-place semantics that separate it from copy_shape-style siblings.

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?

Explicitly routes the agent away from a named alternative: 'use instead of editing Placement via set_property'. It also gives the conditional semantics of relative=True vs False, which is real decision guidance. It does not address other plausible movers (linear_pattern, mirrored, scale_shape), so it falls short of full when/when-not coverage.

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