Skip to main content
Glama
Sign In
Maya MCP

Maya MCP

by science-animated
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_transform

Retrieve a Maya object's world-space translation, rotation, and scale by name to inspect or verify its current scene transform.

Instructions

Get world-space translation, rotation, and scale of a Maya object.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one genuinely useful behavioral fact — values are world-space, not local — and 'Get' implies a non-mutating read, but it says nothing about behavior when the object does not exist or how a name is resolved.

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?

One sentence, front-loaded with the verb and the return contents, with zero filler. Nothing could be removed without losing information.

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 covers the return values, so the description needn't enumerate them. However, with no annotations and an undocumented required parameter, an agent still lacks the name-resolution rules and failure behavior needed to call it confidently.

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

Parameters2/5

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

The single parameter 'name' has 0% schema description coverage, and the description never mentions it. There is no guidance on whether it takes a bare node name, a DAG path, a full path, or how a short name with duplicates is resolved.

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 ('Get') and resource ('transform') plus the exact data returned (world-space translation, rotation, scale) of a Maya object. The 'world-space' qualifier meaningfully separates it from a local-space read or from set_transform, though no sibling is named.

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?

The description gives no when-to-use context: nothing says whether to prefer this over get_attribute (which can also read translate/rotate/scale) or get_object_info, and no prerequisites or error conditions are mentioned. Usage is only implied by the word 'Get'.

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