Skip to main content
Glama

import_generated_asset

Import 3D assets generated by Hyper3D Rodin into Blender scenes using task UUID or request ID parameters.

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 implementation of the import_generated_asset MCP tool. It validates input parameters and delegates the request to Blender via blender.send_command.
    @telemetry_tool("import_generated_asset")
    @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)}"
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions return value ('Return if the asset has been imported successfully'), but omits side effects (where imported?), error behavior, or what 'MAIN_SITE' vs 'FAL_AI' modes entail. Adequate but not rich behavioral disclosure.

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 dedicated Parameters section and clear constraint statement. Slightly awkward phrasing in 'Return if the asset has been imported successfully' but generally efficient with no wasted sentences.

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?

Adequately covers the 3-parameter input signature with complex conditional logic (mode-dependent IDs). References return status. Missing output schema is partially mitigated by success mention, though error formats and destination context (scene specifics) remain undocumented.

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

Parameters5/5

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

Compensates perfectly for 0% schema coverage. Defines all three parameters: 'name' (object name in scene), 'task_uuid' (MAIN_SITE mode), 'request_id' (FAL_AI mode). Critical mutual exclusivity constraint documented: 'Only give one of {task_uuid, request_id}'.

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?

Description states specific verb (Import) + specific resource (asset generated by Hyper3D Rodin) + scope (after generation task completed). Explicitly naming 'Hyper3D Rodin' distinguishes from sibling tool 'import_generated_asset_hunyuan' and from generation tools like 'generate_hyper3d_model_via_images'.

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 parameter usage constraint: 'Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode!' and implies prerequisite timing ('after the generation task is completed'). Lacks explicit cross-reference to alternative import tools (e.g., when to use Hunyuan variant instead).

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