Maya MCP

Overview Schema Source Related Servers Discussions Admin

set_transform

Set or adjust a named Maya object's world-space translation, rotation in degrees, and scale, modifying only the components you supply.

Instructions

Set world-space translation [x,y,z], rotation [rx,ry,rz] (degrees), and/or scale [sx,sy,sz] on an object. All parameters are optional — only the ones provided will be changed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`scale`	No
`rotation`	No
`translation`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden and it does add real value: world-space rather than local, degrees for rotation, and the important guarantee that unspecified components are left untouched. It does not state translation/scale units, what happens if the object name is unknown, or any undo/permission behavior for this mutation.

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, no filler, with the component/unit mapping front-loaded and the partial-update rule as the closing clause. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and the supported components are covered. Still missing for a mutation tool with zero annotation coverage: units for translation and scale, error behavior on a bad name, and consistency with the required 'name' parameter.

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

Parameters3/5

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

Schema coverage is 0% and array items are untyped '{}', so the description is doing necessary work by fixing element order and units ([x,y,z], [rx,ry,rz] in degrees, [sx,sy,sz]). However it omits translation/scale units, whether arrays must be exactly length 3, and never describes 'name' — and it wrongly claims all parameters are optional when the schema requires name.

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?

Names a specific verb (Set) and resource (transform) and enumerates the components it writes: translation, rotation, scale. The 'world-space' qualifier meaningfully separates it from a local-space or attribute-level writer like set_attribute, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

It says what can be changed but never when to reach for this versus set_attribute or get_transform, nor any precondition (object must exist, must be selected, locking). The only usage cue is the partial-update note, which is about mechanics rather than tool selection.

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