Skip to main content
Glama

import_generated_asset_hunyuan

Import 3D assets generated by Hunyuan3D into Blender scenes using the provided 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 main handler function implementing the 'import_generated_asset_hunyuan' MCP tool. It is registered via @mcp.tool(), defines input parameters (name, zip_file_url), and sends the corresponding command to the Blender addon via the connection.
    @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)}"
  • Documentation in the asset_creation_strategy prompt instructing how to use the tool after polling the Hunyuan3D job status.
            - Use import_generated_asset_hunyuan() to import the generated OBJ model the asset
    if Hunyuan3D mode is "LOCAL_API":
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool imports an asset and returns success status, but lacks details on permissions, rate limits, error handling, or what 'imported successfully' entails (e.g., scene placement, format compatibility). For a mutation tool with zero annotation coverage, this is insufficient.

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, followed by parameter details and return statement in three clear sentences. It avoids redundancy but could be slightly more structured (e.g., bullet points for parameters).

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?

Given 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It covers basic purpose and parameters but lacks behavioral details (e.g., side effects, error cases) and output specifics, which are critical for a mutation tool in this context.

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 the description must compensate. It lists parameters with brief explanations ('name of the object in scene', 'zip_file_url given in generate model step'), adding some semantics beyond schema titles. However, it doesn't clarify format constraints (e.g., URL validity, name uniqueness) or usage nuances, leaving gaps for 2 parameters.

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') and the resource ('asset generated by Hunyuan3D'), distinguishing it from generic import tools like 'import_generated_asset' by specifying the Hunyuan3D source. However, it doesn't explicitly differentiate from all siblings beyond naming the source.

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 usage context by mentioning 'after the generation task is completed' and referencing 'zip_file_url given in the generate model step,' which suggests it should be used post-generation with a specific URL. However, it lacks explicit when-not-to-use guidance or named alternatives among siblings.

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

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