Maya MCP

by science-animated

Overview Schema Source Related Servers Discussions Admin

Python

Local

set_attribute

Set an attribute value on a Maya node. Use lists for multi-component attributes to control node properties precisely.

Instructions

Set the value of an attribute on a Maya node. Pass lists for multi-component attrs.

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": {
      "node": "<node>",
      "attribute": "<attribute>",
      "value": "<value>"
    },
    "name": "set_attribute"
  }
}

Input Schema

Name	Required	Description	Default
`node`	Yes
`value`	Yes
`attribute`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden: it doesn't say whether the change is undoable, what happens on an invalid node or attribute name, whether values are coerced, or what the tool returns despite being a mutation. The note "Pass lists for multi-component attrs" is the only behavioral detail, and it conflicts with the schema, which types `value` as a plain string.

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 sentences with the action front-loaded and no filler. The second sentence is terse to the point of ambiguity, but nothing is wasted.

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?

This is a mutating, three-parameter tool with no annotations and zero schema documentation, and an output schema exists so return values needn't be explained. Still, essential facts for correct invocation (attribute naming conventions, type coercion, failure modes, undo behavior) are absent, leaving the agent to guess.

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 all three parameters rely on the description, which only addresses `value` indirectly via the multi-component list note. Nothing explains the expected format of `node` (name vs. path/DAG) or `attribute` (long vs. short name, compound attribute syntax), and the list hint contradicts the declared string type.

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 ("Set the value of an attribute on a Maya node"), which is clearly distinct from get_attribute and set_transform by name and semantics. It lacks an explicit contrast with siblings like execute_maya_code, but the operation is unambiguous.

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?

There is no guidance on when to use this tool versus execute_maya_code, set_transform, or set_material_property, and no prerequisites such as needing the node to exist or the attribute to be unlocked. The only usage hint is the list form for multi-component attributes, which is a syntax note rather than a routing rule.

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