Skip to main content
Glama

maya_import_file

Import OBJ, FBX, GLB/GLTF, Alembic, Maya files, and BVH mocap into Maya with namespace, parent group, and scale options.

Instructions

Import 3D files into Maya: OBJ, FBX, GLB/GLTF, Alembic ABC, Maya MA/MB, BVH mocap. With namespace, parent group, and scale options.

GLB/GLTF: uses Maya's native glTF scene parser (type='glTF Import'); if the parser is not registered or import fails, falls back to the Vision3D sibling pattern — mesh_uv.obj + texture_baked.png next to the GLB — building an aiStandardSurface with the texture in baseColor and assigning it to the imported meshes.

BVH: Maya has no native BVH import, so .bvh motion-capture files are parsed and rebuilt by the pure-Python maya_mcp.bvh_import module (hierarchy → joints, motion → keyframes, with the per-joint BVH→Maya rotate-order mapping handled internally). namespace and scale_factor are forwarded to the builder; the skeleton lands under a <namespace>:bvh_grp group. The result feeds a HumanIK retarget onto a rigged character (mocap → generic animation library).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It details fallback behavior for GLB/GLTF, special handling for BVH (pure-Python parser, HumanIK retarget), and explains namespace/scale_factor forwarding. It doesn't cover error conditions or undo behavior, but it provides substantial behavioral 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?

The description is front-loaded with the main purpose and options, then dives into technical details for specific formats. It is relatively concise given the complexity, though some redundancy exists (e.g., repeated mention of namespace/scale_factor in BVH section). Structure is clear.

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?

Given the tool's complexity (multiple file types with special import logic), the description covers key behaviors. It mentions output implicitly (e.g., BVH leads to HumanIK retarget) but does not discuss return values; however, an output schema exists. It could mention error handling or prerequisites, but overall it is sufficient.

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?

The description mentions namespace, parent group, and scale factor, adding some context (e.g., group_under created if not exists, BVH skeleton under bvh_grp). However, it does not thoroughly describe each parameter beyond what the input schema provides. The schema itself includes descriptions, so no major gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Import 3D files into Maya' and lists supported formats (OBJ, FBX, GLB/GLTF, Alembic ABC, Maya MA/MB, BVH mocap). This distinctively identifies the tool's action and resource, setting it apart from sibling tools like maya_create_primitive or maya_assign_material.

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 description implies when to use the tool (to import external 3D files) but does not explicitly state when not to use it or compare it to alternatives. It provides context for specific formats but lacks general usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abrahamADSK/maya-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server