Skip to main content
Glama

create_3d_model_from_text

Generate 3D models from text descriptions using AI, then monitor task status to retrieve completed assets.

Instructions

Create a 3D model from a text description using the Tripo API.

IMPORTANT: This tool initiates a 3D model generation task but does NOT wait for completion.
After calling this tool, you MUST repeatedly call the get_task_status tool with the returned
task_id until the task status is SUCCESS or a terminal error state.

Typical workflow:
1. Call create_3d_model_from_text to start the task
2. Get the task_id from the response
3. Call get_task_status with the task_id
4. If status is not SUCCESS, wait a moment and call get_task_status again
5. Repeat until status is SUCCESS or a terminal error state
6. When status is SUCCESS, use the pbr_model_url from the response

Args:
    describe_the_look_of_object: A detailed description of the object to generate.
    face_limit: The maximum number of faces in the model.
    auto_size: Whether to automatically size the model.

Returns:
    A dictionary containing the task ID and instructions for checking the status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
describe_the_look_of_objectYes
face_limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for 'create_3d_model_from_text' tool. Decorated with @mcp.tool() which handles both registration and schema generation from the function signature and docstring. Initiates a Tripo API text-to-3D model generation task asynchronously and returns the task_id for subsequent status checks.
    @mcp.tool()
    async def create_3d_model_from_text(
        describe_the_look_of_object: str, face_limit: int = -1
    ) -> Dict[str, Any]:
        """
        Create a 3D model from a text description using the Tripo API.
    
        IMPORTANT: This tool initiates a 3D model generation task but does NOT wait for completion.
        After calling this tool, you MUST repeatedly call the get_task_status tool with the returned
        task_id until the task status is SUCCESS or a terminal error state.
    
        Typical workflow:
        1. Call create_3d_model_from_text to start the task
        2. Get the task_id from the response
        3. Call get_task_status with the task_id
        4. If status is not SUCCESS, wait a moment and call get_task_status again
        5. Repeat until status is SUCCESS or a terminal error state
        6. When status is SUCCESS, use the pbr_model_url from the response
    
        Args:
            describe_the_look_of_object: A detailed description of the object to generate.
            face_limit: The maximum number of faces in the model.
            auto_size: Whether to automatically size the model.
    
        Returns:
            A dictionary containing the task ID and instructions for checking the status.
        """
        # Get the API key from environment variable
        # api_key = os.environ.get("TRIPO_API_KEY")
        get_blender_connection()
        blender = get_blender_connection()
        api_key = _tripo_apikey
        if not api_key:
            raise ValueError(
                "It may take some more time to correctly re-enter the tripo function. You can first check the scene and then try the tripo function again later"
            )
    
        # Create the Tripo client
        async with TripoClient(api_key=api_key) as client:
            # Create a text-to-model task
            task_id = await client.text_to_model(
                prompt=describe_the_look_of_object,
                face_limit=face_limit,
            )
    
            # Get initial task status
            task = await client.get_task(task_id)
    
            # Return immediately with task ID and status
            return {
                "task_id": task_id,
                "status": str(task.status),
                "progress": task.progress,
                "message": "Task created successfully. The 3D model generation is in progress.",
                "next_step": "You MUST now call get_task_status with this task_id to check progress.",
                "important_note": "3D model generation takes 3-5 minutes. You need to repeatedly call get_task_status until completion.",
                "workflow": [
                    "1. You've completed this step by calling create_3d_model_from_text",
                    "2. Now call get_task_status with task_id: " + task_id,
                    "3. If status is not SUCCESS, wait and call get_task_status again",
                    "4. When status is SUCCESS, use the pbr_model_url from the response",
                ],
            }
  • src/server.py:718-718 (registration)
    The @mcp.tool() decorator registers the function as an MCP tool, automatically generating input schema from parameters and output from return type/docstring.
    @mcp.tool()
  • Function signature defining the input schema: describe_the_look_of_object (str, required), face_limit (int, optional default -1). Output is Dict[str, Any].
    async def create_3d_model_from_text(
        describe_the_look_of_object: str, face_limit: int = -1
    ) -> Dict[str, Any]:
Behavior4/5

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

With no annotations provided, the description carries full burden and does an excellent job explaining the asynchronous behavior, workflow requirements, and expected response structure. It discloses that this is an initiation tool requiring follow-up calls, describes the polling pattern, and explains how to access the final result via pbr_model_url.

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 perfectly structured with clear sections: purpose statement, important behavioral note, numbered workflow steps, and parameter/return explanations. Every sentence earns its place by providing essential information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (asynchronous operation requiring workflow coordination) and the presence of an output schema, the description provides complete context. It explains the asynchronous nature, the required follow-up workflow with sibling tools, parameter meanings, and what to expect in responses - covering everything an agent needs to use this tool correctly.

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 description coverage, the description compensates by explaining all 3 parameters mentioned in the Args section. It clarifies what 'describe_the_look_of_object' should contain, what 'face_limit' controls, and what 'auto_size' does. However, the input schema only shows 2 parameters, creating a minor discrepancy with the description mentioning 3.

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 specific action ('Create a 3D model from a text description') and identifies the resource ('using the Tripo API'). It distinguishes this tool from siblings like 'create_3d_model_from_image' by specifying it works from text input rather than images.

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

Usage Guidelines5/5

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

The description provides explicit workflow instructions with numbered steps, including when to use this tool (to initiate generation) and when to use the sibling 'get_task_status' tool (to check completion). It clearly states this tool doesn't wait for completion and must be followed by status checks.

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/VAST-AI-Research/tripo-mcp'

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