Skip to main content
Glama

import_generated_asset_hunyuan

Import 3D assets generated by Hunyuan3D into Blender scenes using a zip file URL and object name for AI-assisted modeling workflows.

Instructions

Import the asset generated by Hunyuan3D after the generation task is completed.

Parameters:

  • name: The name of the object in scene

  • zip_file_url: The zip_file_url given in the generate model step.

Return if the asset has been imported successfully.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
zip_file_urlYes

Implementation Reference

  • The tool `import_generated_asset_hunyuan` is implemented as an MCP tool handler in `src/blender_mcp/server.py`. It uses `@mcp.tool()` for registration and calls the blender server command `import_generated_asset_hunyuan` via `blender.send_command`.
    @mcp.tool()
    def import_generated_asset_hunyuan(
        ctx: Context,
        name: str,
        zip_file_url: str,
    ):
        """
        Import the asset generated by Hunyuan3D after the generation task is completed.
    
        Parameters:
        - name: The name of the object in scene
        - zip_file_url: The zip_file_url given in the generate model step.
    
        Return if the asset has been imported successfully.
        """
        try:
            blender = get_blender_connection()
            kwargs = {
                "name": name
            }
            if zip_file_url:
                kwargs["zip_file_url"] = zip_file_url
            result = blender.send_command("import_generated_asset_hunyuan", kwargs)
            return result
        except Exception as e:
            logger.error(f"Error generating Hunyuan3D task: {str(e)}")
            return f"Error generating Hunyuan3D task: {str(e)}"
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context by specifying the return value indicates import success and establishing the temporal dependency on generation completion. However, it omits details about failure modes, idempotency, or side effects like scene modification.

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 well-structured with clear visual separation between the purpose statement, parameter definitions, and return value description. Every sentence serves a distinct function without redundancy, though the parameter descriptions could be slightly more detailed regarding format constraints.

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?

Given the tool's limited complexity (2 parameters, no output schema) and workflow integration with Hunyuan3D generation, the description provides sufficient baseline information for invocation. However, it leaves gaps regarding error handling, ZIP file content requirements, and behavior when the object name already exists in the scene.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description effectively compensates by providing semantic meaning for both parameters: 'name' clarifies it refers to the object name in the scene, and 'zip_file_url' references its origin in the generation step. These descriptions add necessary context beyond the bare schema titles.

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 clearly states the action (Import), resource (asset generated by Hunyuan3D), and workflow timing (after generation task is completed). It implicitly distinguishes from the sibling 'import_generated_asset' by specifying 'Hunyuan3D', though it doesn't explicitly clarify when to use this variant versus the generic import tool.

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 provides implied usage context by stating 'after the generation task is completed' and referencing 'the generate model step' in the zip_file_url parameter. However, it lacks explicit guidance on when to choose this tool over the sibling 'import_generated_asset' or error handling prerequisites.

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/omniconnexsynapse/blender-mcp'

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