Maya MCP

by science-animated

Overview Schema Source Related Servers Discussions Admin

Python

Local

duplicate_object

Create a copy of a Maya object and optionally rename it, enabling scene iteration and variant creation.

Instructions

Duplicate a Maya object. Optionally rename the duplicate.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`new_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether the duplicate is a copy or an instance, whether history, transforms, or parenting are preserved, how naming collisions are handled, or what side effects occur. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

Two short, front-loaded sentences with no wasted words. The operation is stated first and the optional behavior second, which is appropriately sized for a simple tool, though the sparse content borders on under-specification rather than true conciseness.

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

Completeness2/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 not be explained. However, with no annotations, 0% parameter description coverage, and no disclosure of duplication semantics such as copy versus instance or naming behavior, the description is not complete enough for an agent to call this mutation tool 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?

Schema description coverage is 0%, so the description must compensate for both parameters. It implicitly maps new_name to the optional rename, but never explains that 'name' identifies the source object to duplicate, nor what format or constraints apply. The description adds only marginal meaning beyond the bare schema.

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?

The description states a specific verb and resource ('Duplicate a Maya object') and adds an optional rename behavior, making the operation clear. It does not explicitly distinguish itself from siblings like create_object or rename_object, but the verb 'duplicate' is sufficiently distinct.

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 phrase 'Optionally rename the duplicate' implies the use of new_name, but there is no explicit guidance on when to use this tool versus create_object, nor any stated prerequisites such as the source object needing to exist or be selected. Usage is implied rather than spelled out.

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