Skip to main content
Glama

import_generated_asset

Import 3D assets created with Hyper3D Rodin into Blender scenes using task identifiers from generation steps to complete the workflow.

Instructions

Import the asset generated by Hyper3D Rodin after the generation task is completed.

Parameters:

  • name: The name of the object in scene

  • task_uuid: For Hyper3D Rodin mode MAIN_SITE: The task_uuid given in the generate model step.

  • request_id: For Hyper3D Rodin mode FAL_AI: The request_id given in the generate model step.

Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode! Return if the asset has been imported successfully.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
task_uuidNo
request_idNo

Implementation Reference

  • The import_generated_asset tool is defined and registered in src/blender_mcp/server.py using the @mcp.tool() decorator. It handles the import of generated assets by sending a command to a Blender connection.
    @mcp.tool()
    def import_generated_asset(
        ctx: Context,
        name: str,
        task_uuid: str=None,
        request_id: str=None,
    ):
        """
        Import the asset generated by Hyper3D Rodin after the generation task is completed.
    
        Parameters:
        - name: The name of the object in scene
        - task_uuid: For Hyper3D Rodin mode MAIN_SITE: The task_uuid given in the generate model step.
        - request_id: For Hyper3D Rodin mode FAL_AI: The request_id given in the generate model step.
    
        Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode!
        Return if the asset has been imported successfully.
        """
        try:
            blender = get_blender_connection()
            kwargs = {
                "name": name
            }
            if task_uuid:
                kwargs["task_uuid"] = task_uuid
            elif request_id:
                kwargs["request_id"] = request_id
            result = blender.send_command("import_generated_asset", kwargs)
            return result
        except Exception as e:
            logger.error(f"Error generating Hyper3D task: {str(e)}")
            return f"Error generating Hyper3D task: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden but discloses minimal behavioral traits. It mentions the return value indicates success, but fails to describe side effects (e.g., adds object to scene, downloads files), error conditions, or what happens if both IDs are provided despite the warning.

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?

Well-structured with clear sections for purpose, parameter details, constraints, and return value. Despite the 'Parameters:' header being somewhat redundant with the schema, the content is essential given the lack of schema descriptions. No wasted sentences.

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?

Adequately covers the import workflow prerequisites and return behavior given no output schema, but lacks completeness regarding error handling (e.g., task not found, incomplete generation), coordinate placement in scene, or file format details. Sufficient for basic usage but gaps remain for edge cases.

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?

Effectively compensates for 0% schema description coverage by defining each parameter's semantics: 'name' is the object name in scene, 'task_uuid' maps to MAIN_SITE mode, and 'request_id' maps to FAL_AI mode. Crucially, it documents the mutual exclusivity constraint absent from the schema.

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 tool 'Import[s] the asset generated by Hyper3D Rodin' with specific verb and resource, and distinguishes itself from sibling generation tools (generate_hyper3d_model_via_*) by focusing on the post-completion import step. It could be slightly improved by specifying 'into the Blender scene' rather than assuming context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit workflow guidance ('after the generation task is completed') and critical parameter constraints ('Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode!'). However, it lacks explicit 'when not to use' guidance (e.g., if generation failed or is pending).

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

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