Skip to main content
Glama
KorwinTeo

BlenderMCP

by KorwinTeo

generate_hyper3d_model_via_images

Generate a 3D model from input images and import it into Blender with built-in materials. Use image paths or URLs to create a normalized-size asset.

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
user_promptNo
bbox_conditionNo
input_image_urlsNo
input_image_pathsNo
Behavior4/5

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

With no annotations, the description carries the full burden and discloses useful behavior: built-in materials, normalized size, and a return message. It does not mention asynchronous behavior or the need to poll job status, which is a minor gap given sibling tools, but the core side effects are covered.

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 brief intro and a parameter breakdown. All sentences contribute useful information, though the parameter section is somewhat dense and could be tightened.

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?

The description covers purpose, input modes, output, and post-generation properties, but misses user_prompt, lacks clarity on whether it submits a job or completes generation, and does not explain the relationship to poll_rodin_job_status. These gaps prevent it from being fully complete.

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

Parameters3/5

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

The description thoroughly explains three of four parameters, including absolute paths, list wrapping, and bbox condition constraints. However, user_prompt is completely omitted, and schema coverage is 0%, leaving a gap for that parameter.

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: generating a 3D asset from images via Hyper3D and importing it into Blender. It uses a specific verb and resource, and distinguishes from sibling tools like generate_hyper3d_model_via_text and import_generated_asset.

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 input_image_paths versus input_image_urls based on the Hyper3D Rodin mode, and explicitly states only one should be given. It does not explicitly mention when to use this tool over generate_hyper3d_model_via_text, but that is implied by the input type.

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

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