Skip to main content
Glama
Eminemminem

BlenderMCP

by Eminemminem

poll_rodin_job_status

Monitor Hyper3D Rodin generation task completion status in BlenderMCP to determine when 3D models are ready for use or if processing has failed.

Instructions

Check if the Hyper3D Rodin generation task is completed.

For Hyper3D Rodin mode MAIN_SITE: Parameters: - subscription_key: The subscription_key given in the generate model step.

Returns a list of status. The task is done if all status are "Done".
If "Failed" showed up, the generating process failed.
This is a polling API, so only proceed if the status are finally determined ("Done" or "Canceled").

For Hyper3D Rodin mode FAL_AI: Parameters: - request_id: The request_id given in the generate model step.

Returns the generation task status. The task is done if status is "COMPLETED".
The task is in progress if status is "IN_PROGRESS".
If status other than "COMPLETED", "IN_PROGRESS", "IN_QUEUE" showed up, the generating process might be failed.
This is a polling API, so only proceed if the status are finally determined ("COMPLETED" or some failed state).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_keyNo
request_idNo

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers and implements the poll_rodin_job_status tool. It handles input parameters (subscription_key or request_id), connects to Blender, sends the poll command, and returns the status result or error.
    @mcp.tool()
    def poll_rodin_job_status(
        ctx: Context,
        subscription_key: str=None,
        request_id: str=None,
    ):
        """
        Check if the Hyper3D Rodin generation task is completed.
    
        For Hyper3D Rodin mode MAIN_SITE:
            Parameters:
            - subscription_key: The subscription_key given in the generate model step.
    
            Returns a list of status. The task is done if all status are "Done".
            If "Failed" showed up, the generating process failed.
            This is a polling API, so only proceed if the status are finally determined ("Done" or "Canceled").
    
        For Hyper3D Rodin mode FAL_AI:
            Parameters:
            - request_id: The request_id given in the generate model step.
    
            Returns the generation task status. The task is done if status is "COMPLETED".
            The task is in progress if status is "IN_PROGRESS".
            If status other than "COMPLETED", "IN_PROGRESS", "IN_QUEUE" showed up, the generating process might be failed.
            This is a polling API, so only proceed if the status are finally determined ("COMPLETED" or some failed state).
        """
        try:
            blender = get_blender_connection()
            kwargs = {}
            if subscription_key:
                kwargs = {
                    "subscription_key": subscription_key,
                }
            elif request_id:
                kwargs = {
                    "request_id": request_id,
                }
            result = blender.send_command("poll_rodin_job_status", kwargs)
            return result
        except Exception as e:
            logger.error(f"Error generating Hyper3D task: {str(e)}")
            return f"Error generating Hyper3D task: {str(e)}"
  • The function signature and docstring define the input schema (subscription_key or request_id optional strings) and describe input/output behavior for different modes.
    def poll_rodin_job_status(
        ctx: Context,
        subscription_key: str=None,
        request_id: str=None,
    ):
        """
        Check if the Hyper3D Rodin generation task is completed.
    
        For Hyper3D Rodin mode MAIN_SITE:
            Parameters:
            - subscription_key: The subscription_key given in the generate model step.
    
            Returns a list of status. The task is done if all status are "Done".
            If "Failed" showed up, the generating process failed.
            This is a polling API, so only proceed if the status are finally determined ("Done" or "Canceled").
    
        For Hyper3D Rodin mode FAL_AI:
            Parameters:
            - request_id: The request_id given in the generate model step.
    
            Returns the generation task status. The task is done if status is "COMPLETED".
            The task is in progress if status is "IN_PROGRESS".
            If status other than "COMPLETED", "IN_PROGRESS", "IN_QUEUE" showed up, the generating process might be failed.
            This is a polling API, so only proceed if the status are finally determined ("COMPLETED" or some failed state).
        """
  • The @mcp.tool() decorator registers the poll_rodin_job_status function as an MCP tool.
    @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 effectively describes the tool's polling nature, expected return values (lists of status or single status), success/failure conditions, and when to proceed based on final status determination. It doesn't mention rate limits, authentication needs, or error handling specifics, but covers core operational behavior well.

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 appropriately sized and well-structured with clear sections for different modes. Every sentence adds value, though it could be slightly more front-loaded by stating the dual-mode nature earlier. The information density is high with no wasted words.

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 the tool's complexity (dual modes with different parameters and status interpretations), no annotations, and no output schema, the description provides substantial context. It explains what the tool returns, how to interpret results, and when to use it. It could potentially mention error cases or timeout behavior for completeness, but covers the essential operational context well.

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?

With 0% schema description coverage and 2 parameters, the description fully compensates by explaining the semantics of both parameters. It clearly states that 'subscription_key' is used for MAIN_SITE mode (given in generate model step) and 'request_id' is used for FAL_AI mode (given in generate model step), adding crucial context beyond the bare 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: 'Check if the Hyper3D Rodin generation task is completed.' It specifies the exact action (checking completion status) and resource (Hyper3D Rodin generation task), and distinguishes it from sibling tools like 'get_hyper3d_status' by focusing specifically on Rodin job polling.

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 guidance on when to use this tool: 'This is a polling API, so only proceed if the status are finally determined.' It also distinguishes between two modes (MAIN_SITE and FAL_AI) with different parameters and status interpretations, offering clear alternatives within the tool itself based on context.

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

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