Skip to main content
Glama

generate_hyper3d_model_via_text

Create 3D models from text descriptions and import them into Blender with built-in materials. Use text prompts to generate assets and optional bounding boxes to control dimensions.

Instructions

Generate 3D asset using Hyper3D by giving description of the desired asset, and import the 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:

  • text_prompt: A short description of the desired model in English.

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

Returns a message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
text_promptYes
bbox_conditionNo

Implementation Reference

  • The implementation of the `generate_hyper3d_model_via_text` tool, which registers with the MCP server and triggers a Hyper3D job via a Blender connection.
    @telemetry_tool("generate_hyper3d_model_via_text")
    @mcp.tool()
    def generate_hyper3d_model_via_text(
        ctx: Context,
        text_prompt: str,
        bbox_condition: list[float]=None
    ) -> str:
        """
        Generate 3D asset using Hyper3D by giving description of the desired asset, and import the 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:
        - text_prompt: A short description of the desired model in **English**.
        - bbox_condition: Optional. If given, it has to be a list of floats of length 3. Controls the ratio between [Length, Width, Height] of the model.
    
        Returns a message indicating success or failure.
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("create_rodin_job", {
                "text_prompt": text_prompt,
                "images": None,
                "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)}"
Behavior3/5

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

Discloses material properties, normalized sizing needs, and auto-import behavior. However, fails to mention asynchronous/job-based nature despite existence of poll_rodin_job_status and get_hyper3d_status siblings, which is critical behavioral context given the annotation absence.

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?

Clear three-part structure (purpose/behavior, parameters, returns). Front-loaded with primary action. No redundant sentences. Parameters section uses informal but readable formatting rather than strict schema documentation style.

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?

Adequate for basic invocation but omits critical workflow context: job polling mechanics implied by sibling tools, Hyper3D service availability checks, and Blender session requirements. Return value description is minimal but acceptable given lack of output schema.

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?

With 0% schema coverage, description fully compensates by explaining both parameters: text_prompt constraints (English, short) and bbox_condition format (list of 3 floats, ratio meaning). Could elaborate on valid value ranges or coordinate system for bbox.

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?

States specific action (Generate 3D asset), identifies service (Hyper3D), and discloses key side effect (import into Blender). Differentiates implicitly from image-based sibling via 'giving description' phrasing, though explicit contrast with generate_hyper3d_model_via_images would strengthen this to a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies text-to-3D use case through parameter descriptions, but lacks explicit 'when to use' guidance or contrast with generate_hunyuan3d_model or image-based alternatives. No mention of workflow prerequisites (e.g., Blender running).

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

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