Skip to main content
Glama
clanker25
by clanker25

generate_hyper3d_model_via_images

Turn reference images into a complete 3D asset with built-in materials, then import it directly into Blender for immediate use. Provide image paths or URLs to generate and load the model, with optional size ratio control.

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.
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the asset has built-in materials, the model is normalized in size, and the tool imports into Blender. However, it does not mention that generation may be asynchronous (given the sibling poll_rodin_job_status) or any prerequisites (e.g., addon status). The mention of mode-dependent requirements is useful but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the core purpose, followed by essential behavioral notes and a detailed parameter list. Every sentence adds value, especially given the low schema coverage. There is no fluff or repetition.

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?

While the parameter semantics are strong, the description omits the asynchronous workflow: it doesn't mention that generation might require polling via poll_rodin_job_status, nor does it explain how to determine the current Rodin mode. The output is described only as a success/failure message, which is acceptable given the output schema exists, but the overall workflow is incomplete for a complex multi-step process.

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 coverage is 0%, so the description must compensate, and it does thoroughly. Each parameter is explained with concrete details: absolute paths vs URLs, wrapping single inputs in lists, bbox_condition format and meaning, and the user_prompt rule about verbatim quoting and repetition. This adds substantial meaning beyond the raw 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: generating a 3D asset from images via Hyper3D and importing it into Blender. It distinguishes itself from the sibling generate_hyper3d_model_via_text by explicitly mentioning 'via images', making the verb and resource unambiguous.

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 guidance on parameter selection (only one of input_image_paths/input_image_urls should be given, depending on Rodin mode), but it does not explicitly contrast with the text-based alternative or state when to choose this tool over it. The purpose statement implies usage, but exclusions and alternatives are not named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.