Skip to main content
Glama

generate_hyper3d_model_via_images

Create 3D models with built-in materials from images and import them directly 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 handler function that executes the tool logic: processes input image paths or URLs, validates them, encodes images if from paths, normalizes bbox_condition, sends 'create_rodin_job' command to Blender addon, and returns task UUID and subscription key or error.
    @telemetry_tool("generate_hyper3d_model_via_images")
    @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)}"
  • Supporting utility function used in the handler to normalize the bbox_condition input into a list of integers scaled to 0-100 range based on the maximum value.
    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
  • Decorators that register the tool with the MCP server (@mcp.tool()) and add telemetry tracking (@telemetry_tool).
    @telemetry_tool("generate_hyper3d_model_via_images")
    @mcp.tool()
  • Input schema and documentation defined in the function docstring, describing parameters, usage constraints, and return format for the MCP tool.
    """
    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.
    """
Behavior4/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 effectively describes key behaviors: the tool generates a 3D asset with built-in materials, imports it into Blender, normalizes the model size (suggesting re-scaling may be needed), and returns a success/failure message. It also clarifies the mode-dependent parameter requirements. However, it lacks details on error conditions, processing time, or Blender integration specifics.

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 and appropriately sized, with a clear purpose statement followed by parameter details. Every sentence adds value, such as explaining material properties and normalization. However, it could be slightly more front-loaded by moving the parameter section after the purpose, and minor wording like 'wanted asset' could be tightened to 'desired asset' for better clarity.

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?

Given the complexity (3D generation and import), no annotations, 0% schema coverage, and no output schema, the description does a strong job. It covers purpose, parameters with semantics, behavioral traits (materials, normalization, return message), and mode dependencies. It could improve by detailing output format beyond success/failure or error handling, but overall it provides sufficient context for effective tool use.

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?

Schema description coverage is 0%, so the description must compensate fully. It provides essential semantics: input_image_paths requires absolute paths and must be a list even for one image, input_image_urls requires URLs similarly wrapped, and bbox_condition is optional with a specific format (list of 3 ints controlling Length, Width, Height ratio). It also explains the exclusive choice between input_image_paths and input_image_urls based on Hyper3D Rodin mode, adding critical usage context not in the schema.

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?

The description clearly states the tool's purpose: 'Generate 3D asset using Hyper3D by giving images of the wanted asset, and import the generated asset into Blender.' It specifies the verb (generate and import), resource (3D asset via Hyper3D), and distinguishes from siblings like generate_hyper3d_model_via_text (images vs. text) and import_generated_asset (which lacks generation).

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 for usage: it specifies that input_image_paths is required for MAIN_SITE mode and input_image_urls for FAL_AI mode, and that only one of these should be given. However, it does not explicitly state when to use this tool over alternatives like generate_hunyuan3d_model or download_polyhaven_asset, nor does it mention prerequisites or exclusions beyond the mode dependency.

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

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