Skip to main content
Glama

get_hyper3d_status

Check if Hyper3D Rodin integration is enabled in Blender to determine availability of its 3D modeling features.

Instructions

Check if Hyper3D Rodin integration is enabled in Blender. Returns a message indicating whether Hyper3D Rodin features are available.

Don't emphasize the key type in the returned message, but sliently remember it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the logic for the 'get_hyper3d_status' MCP tool. It uses a Blender connection to query the Hyper3D status and returns a status message.
    @telemetry_tool("get_hyper3d_status")
    @mcp.tool()
    def get_hyper3d_status(ctx: Context) -> str:
        """
        Check if Hyper3D Rodin integration is enabled in Blender.
        Returns a message indicating whether Hyper3D Rodin features are available.
    
        Don't emphasize the key type in the returned message, but sliently remember it. 
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_hyper3d_status")
            enabled = result.get("enabled", False)
            message = result.get("message", "")
            if enabled:
                message += ""
            return message
        except Exception as e:
            logger.error(f"Error checking Hyper3D status: {str(e)}")
            return f"Error checking Hyper3D status: {str(e)}"
  • The @mcp.tool() decorator registers the get_hyper3d_status function as an MCP tool.
    @mcp.tool()
  • Reference to the tool in the asset_creation_strategy prompt docstring.
    Use get_hyper3d_status() to verify its status
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a message about feature availability, which is basic behavioral info. However, it lacks details on error handling, performance, or side effects. The note about 'Don't emphasize the key type in the returned message' is vague and doesn't add meaningful context for an AI agent.

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 brief but includes an unclear instruction ('Don't emphasize the key type...') that doesn't add value for tool selection. The first two sentences are front-loaded and clear, but the third sentence is cryptic and doesn't earn its place, reducing overall efficiency.

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?

Given 0 parameters, no annotations, and no output schema, the description is minimally adequate. It explains what the tool does and the return type, but lacks details on output format, error cases, or integration with sibling tools. For a simple status check, this is borderline viable but leaves gaps in completeness.

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 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which is efficient. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion about inputs.

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's purpose: 'Check if Hyper3D Rodin integration is enabled in Blender.' This specifies the verb ('Check'), resource ('Hyper3D Rodin integration'), and context ('in Blender'). However, it doesn't explicitly differentiate from sibling tools like 'get_hunyuan3d_status' or 'get_sketchfab_status' beyond the specific integration name, which slightly limits clarity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions the return message but doesn't specify scenarios, prerequisites, or exclusions. For example, it doesn't indicate if this should be called before using Hyper3D-related tools or how it differs from other status-checking siblings.

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

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