Skip to main content
Glama

import_generated_asset

Import 3D models generated by Hyper3D Rodin into Blender scenes using task UUID or request ID parameters for different generation modes.

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 core handler function for the 'import_generated_asset' tool, decorated with @mcp.tool() for MCP registration. It handles input parameters, constructs kwargs, sends the import command to the Blender connection, and returns the result or error.
    @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)}"
  • The docstring provides the input schema description, parameter details, and usage instructions for the tool.
    """
    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.
    """
  • Reference in the asset_creation_strategy prompt explaining usage of the tool post-generation.
        - Use import_generated_asset() to import the generated GLB model the asset
    4. After importing the asset, ALWAYS check the world_bounding_box of the imported mesh, and adjust the mesh's location and size
        Adjust the imported mesh's location, scale, rotation, so that the mesh is on the right spot.
  • The @mcp.tool() decorator registers the function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions that the tool imports an asset and returns success status, but lacks details on permissions, error handling, rate limits, or what 'import' entails (e.g., where the asset is stored, if it overwrites existing assets). For a mutation tool with zero annotation coverage, this is a significant gap in 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?

The description is appropriately sized and front-loaded with the main purpose. The parameter explanations are necessary given the lack of schema descriptions. However, the last sentence about the return value could be integrated more smoothly, and there's minor redundancy in specifying 'Hyper3D Rodin' multiple times.

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 complexity (mutation tool with 3 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose, usage context, and parameter semantics adequately, but lacks details on behavioral aspects like error cases, side effects, or output format. For a tool that performs an import operation, more context on what 'successfully' means would be beneficial.

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?

Schema description coverage is 0%, so the description must compensate. It adds crucial semantic information: 'name' is the object name in the scene, 'task_uuid' is for MAIN_SITE mode from a generate step, and 'request_id' is for FAL_AI mode from a generate step. It also specifies the exclusive choice between task_uuid and request_id. This goes well beyond the bare schema, though it doesn't cover all possible nuances (e.g., format of IDs).

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 Hyper3D Rodin'), making the purpose understandable. It distinguishes from siblings by specifying it's for assets generated by Hyper3D Rodin, not downloaded from external sources like Polyhaven or Sketchfab. However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

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?

The description provides clear context on when to use this tool: after a generation task is completed in Hyper3D Rodin, and it specifies which parameter to use based on the mode (MAIN_SITE vs FAL_AI). It doesn't explicitly state when NOT to use it or name alternatives, but the context is sufficient for informed usage.

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/johncarlo177/Python.BlenderMCP'

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