Skip to main content
Glama
opslon

BlenderMCP

by opslon

import_generated_asset_hunyuan

Import 3D assets from Hunyuan3D into Blender by providing the object name and zip file URL from completed generation tasks.

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 handler function that implements the import_generated_asset_hunyuan tool logic.
    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)}"
  • The registration of the import_generated_asset_hunyuan tool using the @mcp.tool decorator.
    @mcp.tool()
    def import_generated_asset_hunyuan(
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 needed, side effects (e.g., whether it modifies existing assets), error handling, or rate limits. Minimal behavioral context is given.

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. It's appropriately sized with no redundant sentences, though the parameter explanations could be more integrated into the flow.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on error cases, what 'successfully' entails, and how this tool fits with siblings like 'generate_hunyuan3d_model' or 'poll_hunyuan_job_status'. More context is needed for a mutation tool.

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 lists parameters with brief explanations ('name of object in scene', 'zip_file_url given in generate model step'), adding meaning beyond schema titles. However, it doesn't detail format constraints or examples, leaving gaps for a tool with 2 required 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'), specifying it's for assets after generation task completion. It distinguishes from sibling 'import_generated_asset' by specifying 'Hunyuan' context, though not explicitly contrasting with other import/download tools.

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?

No explicit guidance on when to use this tool versus alternatives like 'import_generated_asset' or download tools. It mentions the asset is from Hunyuan3D and after generation, but lacks clear when-not-to-use scenarios or prerequisites beyond implied context.

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

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