Maya MCP

Overview Schema Source Related Servers Discussions Admin

get_object_info

Query detailed Maya object data—transforms, bounding box, materials, hierarchy—to inspect scene structure and guide modifications.

Instructions

Get detailed information about a specific Maya object: transforms, bounding box, materials, hierarchy.

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

Input Schema

Name	Required	Description	Default
`object_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries more burden, but 'Get' reasonably implies a read-only operation and the listed categories clarify what information is inspected. It does not state preconditions such as whether the object must exist, error behavior, or any permissions/rate context.

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?

A single front-loaded sentence with no wasted words. It is appropriately sized for a simple read tool, though it could be slightly more informative without losing concision.

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?

The output schema covers return values, and the description usefully lists returned categories. However, for a tool with no annotations and an undocumented parameter, the description leaves gaps around parameter format and when to prefer sibling tools.

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%, and the description does not explain the sole parameter object_name beyond the phrase 'specific Maya object.' It does not specify expected naming format, whether names must be unique, or how to reference hierarchy paths.

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 and resource ('Get detailed information about a specific Maya object') and enumerates the kinds of information returned. It implicitly differentiates from scene-level siblings like get_scene_info, but does not explicitly distinguish from get_transform or get_attribute.

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 implies usage by saying it gets detailed object information, but gives no explicit when-to-use guidance, exclusions, or alternatives such as get_transform for only transforms. It leaves routing between related sibling tools to inference.

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