Skip to main content
Glama

generate_hyper3d_model_via_images

Create 3D models with materials from images and import them into Blender for 3D modeling workflows.

Instructions

Generate 3D asset using Hyper3D by giving images of the wanted asset, and import the generated asset into Blender. The 3D asset has built-in materials. The generated model has a normalized size, so re-scaling after generation can be useful.

Parameters:

  • input_image_paths: The absolute paths of input images. Even if only one image is provided, wrap it into a list. Required if Hyper3D Rodin in MAIN_SITE mode.

  • input_image_urls: The URLs of input images. Even if only one image is provided, wrap it into a list. Required if Hyper3D Rodin in FAL_AI mode.

  • bbox_condition: Optional. If given, it has to be a list of ints of length 3. Controls the ratio between [Length, Width, Height] of the model.

Only one of {input_image_paths, input_image_urls} should be given at a time, depending on the Hyper3D Rodin's current mode. Returns a message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_image_pathsNo
input_image_urlsNo
bbox_conditionNo

Implementation Reference

  • The @mcp.tool()-decorated handler function that implements the core logic for generating a Hyper3D model from images. It validates inputs, encodes images if from paths, sends a 'create_rodin_job' command to Blender via socket, and returns task details or error.
    @mcp.tool()
    def generate_hyper3d_model_via_images(
        ctx: Context,
        input_image_paths: list[str]=None,
        input_image_urls: list[str]=None,
        bbox_condition: list[float]=None
    ) -> str:
        """
        Generate 3D asset using Hyper3D by giving images of the wanted asset, and import the generated asset into Blender.
        The 3D asset has built-in materials.
        The generated model has a normalized size, so re-scaling after generation can be useful.
        
        Parameters:
        - input_image_paths: The **absolute** paths of input images. Even if only one image is provided, wrap it into a list. Required if Hyper3D Rodin in MAIN_SITE mode.
        - input_image_urls: The URLs of input images. Even if only one image is provided, wrap it into a list. Required if Hyper3D Rodin in FAL_AI mode.
        - bbox_condition: Optional. If given, it has to be a list of ints of length 3. Controls the ratio between [Length, Width, Height] of the model.
    
        Only one of {input_image_paths, input_image_urls} should be given at a time, depending on the Hyper3D Rodin's current mode.
        Returns a message indicating success or failure.
        """
        if input_image_paths is not None and input_image_urls is not None:
            return f"Error: Conflict parameters given!"
        if input_image_paths is None and input_image_urls is None:
            return f"Error: No image given!"
        if input_image_paths is not None:
            if not all(os.path.exists(i) for i in input_image_paths):
                return "Error: not all image paths are valid!"
            images = []
            for path in input_image_paths:
                with open(path, "rb") as f:
                    images.append(
                        (Path(path).suffix, base64.b64encode(f.read()).decode("ascii"))
                    )
        elif input_image_urls is not None:
            if not all(urlparse(i) for i in input_image_paths):
                return "Error: not all image URLs are valid!"
            images = input_image_urls.copy()
        try:
            blender = get_blender_connection()
            result = blender.send_command("create_rodin_job", {
                "text_prompt": None,
                "images": images,
                "bbox_condition": _process_bbox(bbox_condition),
            })
            succeed = result.get("submit_time", False)
            if succeed:
                return json.dumps({
                    "task_uuid": result["uuid"],
                    "subscription_key": result["jobs"]["subscription_key"],
                })
            else:
                return json.dumps(result)
        except Exception as e:
            logger.error(f"Error generating Hyper3D task: {str(e)}")
            return f"Error generating Hyper3D task: {str(e)}"
  • Helper function used by the tool to process and normalize the bbox_condition parameter into a list of integers scaled to 0-100.
    def _process_bbox(original_bbox: list[float] | list[int] | None) -> list[int] | None:
        if original_bbox is None:
            return None
        if all(isinstance(i, int) for i in original_bbox):
            return original_bbox
        if any(i<=0 for i in original_bbox):
            raise ValueError("Incorrect number range: bbox must be bigger than zero!")
        return [int(float(i) / max(original_bbox) * 100) for i in original_bbox] if original_bbox else None
  • The docstring within the handler provides the input schema/validation details and usage instructions for the tool parameters.
    """
    Generate 3D asset using Hyper3D by giving images of the wanted asset, and import the generated asset into Blender.
    The 3D asset has built-in materials.
    The generated model has a normalized size, so re-scaling after generation can be useful.
    
    Parameters:
    - input_image_paths: The **absolute** paths of input images. Even if only one image is provided, wrap it into a list. Required if Hyper3D Rodin in MAIN_SITE mode.
    - input_image_urls: The URLs of input images. Even if only one image is provided, wrap it into a list. Required if Hyper3D Rodin in FAL_AI mode.
    - bbox_condition: Optional. If given, it has to be a list of ints of length 3. Controls the ratio between [Length, Width, Height] of the model.
    
    Only one of {input_image_paths, input_image_urls} should be given at a time, depending on the Hyper3D Rodin's current mode.
    Returns a message indicating success or failure.
  • The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the generation process, import into Blender, built-in materials, and normalized size, which are useful behavioral traits. However, it doesn't mention important aspects like whether this is a long-running operation, what permissions are needed, error handling, or what the success/failure messages contain. The description adds value but leaves significant gaps in behavioral understanding.

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 well-structured with a clear opening statement followed by a dedicated parameters section. Each sentence adds value, though the middle section about materials and scaling could be more tightly integrated. It's appropriately sized for a tool with 3 parameters and complex behavior, with no redundant information.

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 tool's complexity (3D generation from images, import to Blender, multiple modes), no annotations, and no output schema, the description provides good parameter coverage but lacks important context. It doesn't explain the return value beyond 'success or failure' message, doesn't mention performance characteristics, error conditions, or how this integrates with the broader 3D workflow alongside sibling tools. The description is adequate but has clear gaps for a tool of this complexity.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter semantics. It explains the purpose of input_image_paths and input_image_urls, their relationship to Hyper3D Rodin modes, the requirement to wrap single images in lists, and the optional bbox_condition with its format and effect. This adds substantial meaning beyond what the bare schema provides.

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 generates a 3D asset using Hyper3D from images and imports it into Blender, with specific details about built-in materials and normalized size. It distinguishes from sibling 'generate_hyper3d_model_via_text' by specifying image-based input, but doesn't fully differentiate from other 3D-related tools like 'import_generated_asset' or 'download_polyhaven_asset' in terms of when to choose this specific approach.

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 about when to use input_image_paths vs input_image_urls based on Hyper3D Rodin's mode (MAIN_SITE vs FAL_AI), and mentions re-scaling after generation can be useful. However, it doesn't explicitly state when to use this tool versus alternatives like 'generate_hyper3d_model_via_text' or other 3D asset acquisition tools, nor does it mention any prerequisites or exclusions.

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