Maya MCP

Overview Schema Source Related Servers Discussions Admin

list_attributes

Lists attributes on a Maya node and filters to keyable attributes when keyable=true, helping inspect node properties for scene queries and automation.

Instructions

List attributes on a Maya node. Set keyable=true to list only keyable attributes.

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

Input Schema

Name	Required	Description	Default
`node`	Yes
`keyable`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

A3.5/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 behavioral burden. 'List' implies a read-only, non-mutating operation, but the description never confirms that or mentions anything about scope, node validity, or behavior on missing nodes; the output schema covers the return shape.

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 no filler, and the core action is front-loaded. The keyable hint sits in a natural second position.

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?

This is a simple two-parameter read tool with an output schema, so return values need no explanation. The only real gap is the undefined node argument, which 0% schema coverage leaves unaddressed.

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 description coverage is 0%, so the description must compensate. It does explain the keyable flag's effect ('list only keyable attributes'), but the required 'node' parameter is left entirely undefined — no format or example of what a valid node reference looks like.

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 ('List attributes') and scopes it to 'a Maya node'. It is distinguishable from sibling get_attribute, which reads a single value, 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 Guidelines3/5

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

Usage is implied rather than stated: the keyable=true hint suggests a filtering use case, but there is no explicit when-to-use guidance or comparison against get_attribute / get_object_info. An agent can infer purpose but not the boundaries.

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