Skip to main content
Glama

poll_hunyuan_job_status

Check the completion status of a Hunyuan3D generation task in Blender, returning the 3D model file path when ready.

Instructions

Check if the Hunyuan3D generation task is completed.

For Hunyuan3D: Parameters: - job_id: The job_id given in the generate model step.

Returns the generation task status. The task is done if status is "DONE".
The task is in progress if status is "RUN".
If status is "DONE", returns ResultFile3Ds, which is the generated ZIP model path
When the status is "DONE", the response includes a field named ResultFile3Ds that contains the generated ZIP file path of the 3D model in OBJ format.
This is a polling API, so only proceed if the status are finally determined ("DONE" or some failed state).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idNo

Implementation Reference

  • Implementation of the poll_hunyuan_job_status tool, which uses blender.send_command to query the job status.
    def poll_hunyuan_job_status(
        ctx: Context,
        job_id: str=None,
    ):
        """
        Check if the Hunyuan3D generation task is completed.
    
        For Hunyuan3D:
            Parameters:
            - job_id: The job_id given in the generate model step.
    
            Returns the generation task status. The task is done if status is "DONE".
            The task is in progress if status is "RUN".
            If status is "DONE", returns ResultFile3Ds, which is the generated ZIP model path
            When the status is "DONE", the response includes a field named ResultFile3Ds that contains the generated ZIP file path of the 3D model in OBJ format.
            This is a polling API, so only proceed if the status are finally determined ("DONE" or some failed state).
        """
        try:
            blender = get_blender_connection()
            kwargs = {
                "job_id": job_id,
            }
            result = blender.send_command("poll_hunyuan_job_status", kwargs)
            return result
        except Exception as e:
  • Registration of the poll_hunyuan_job_status tool using the @mcp.tool() decorator.
    @mcp.tool()
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 successfully explains the state machine (DONE vs RUN vs failed), reveals the specific return structure (ResultFile3Ds containing a ZIP path), discloses the file format (OBJ), and characterizes the polling nature of the API.

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

Conciseness3/5

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

The description is front-loaded with the purpose but contains redundancy: it describes ResultFile3Ds twice in consecutive sentences with slightly different wording. The 'Parameters:' section uses unusual indentation. The information is valuable but could be more efficiently structured.

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 no output schema exists, the description appropriately explains return values (status strings and ResultFile3Ds field). It covers the essential polling workflow and completion states necessary for an agent to use this tool effectively within the Hunyuan3D job lifecycle.

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?

The input schema has 0% description coverage for the job_id parameter. The description compensates adequately by explaining that job_id is 'The job_id given in the generate model step', providing semantic context about the parameter's source and relationship to the workflow.

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?

The description clearly states the tool 'Check[s] if the Hunyuan3D generation task is completed' and identifies itself as a 'polling API'. It distinguishes from the generation step (sibling generate_hunyuan3d_model) by referencing 'the job_id given in the generate model step'. However, it does not clarify when to use this versus the sibling get_hunyuan3d_status.

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?

The description provides implicit workflow guidance by explaining the status values ('DONE', 'RUN', failed states) and advising to proceed only when status is finally determined. However, it lacks explicit when/when-not guidance compared to alternatives like get_hunyuan3d_status, and the 'only proceed' phrasing is slightly ambiguous.

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