Skip to main content
Glama

poll_rodin_job_status

Check if a Hyper3D Rodin generation task is completed by polling its status, returning completion, progress, or failure.

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
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses return format (list of status for MAIN_SITE, single status for FAL_AI), status meanings, and when to consider task complete or failed. Could mention idempotency or side effects, but behavior is well-covered.

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?

Well-structured with a clear introductory sentence and two mode-specific sections. Slightly verbose (could merge common parts), but each sentence adds value. Front-loaded purpose.

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, description covers return values, status meanings, and failure conditions. It lacks polling interval advice or typical latency, but is otherwise complete for a polling tool. Mode-specific details add thoroughness.

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 description coverage is 0%, so description adds full meaning. It explains 'subscription_key' and 'request_id' as coming from the generate step, and clarifies conditional usage per mode. This compensates completely for the lack of schema descriptions.

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 'Check if the Hyper3D Rodin generation task is completed' with specific verb and resource. It distinguishes two modes (MAIN_SITE vs FAL_AI) and differentiates from sibling tools like 'get_hyper3d_status' by focusing on polling completion status.

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?

Provides explicit context for when to use the tool: after the generate model step. Explains which parameter to use for each mode and how to interpret statuses. Lacks explicit exclusions or alternative tool recommendations, but the polling guidance is clear.

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/Gorav22/Blender-mcp'

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