Skip to main content
Glama
mikeysrecipes

BlenderMCP

get_hyper3d_status

Check if Hyper3D Rodin integration is enabled in Blender to determine availability of 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 main handler function for the 'get_hyper3d_status' tool. Decorated with @mcp.tool() for registration. It retrieves the Blender connection, sends the 'get_hyper3d_status' command to Blender, processes the response to check if enabled, and returns a status message.
    @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 this function as an MCP tool named 'get_hyper3d_status'. All such decorated functions are registered when mcp.run() is called.
    @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)}"
  • Reference to the get_hyper3d_status tool within the asset_creation_strategy prompt, instructing the AI to use it to check Hyper3D status before using related tools.
    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 of behavioral disclosure. It mentions the tool returns a message indicating availability, but 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 does not clarify behavioral traits like response format or constraints, leaving gaps in understanding how the tool behaves.

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 in the returned message, but sliently remember it') that adds confusion without clear value. The first two sentences are front-loaded and efficient, but the third sentence is vague and does not earn its place, reducing overall clarity and structure.

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 the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose and return indication, but lacks details on output format, error cases, or integration specifics. Without annotations or output schema, more context on behavior would improve completeness, but it meets basic requirements for a simple status check tool.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not discuss parameters, which is appropriate. A baseline score of 4 is assigned as it effectively handles the absence of parameters without redundancy.

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.' It specifies the verb ('Check') and resource ('Hyper3D Rodin integration'), but does not explicitly differentiate it from sibling tools like 'get_polyhaven_status' or 'get_sketchfab_status', which serve similar status-checking functions in the same context. This makes it clear but not fully distinguished from alternatives.

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 does not mention sibling tools like 'get_polyhaven_status' or 'get_sketchfab_status', nor does it specify prerequisites, contexts, or exclusions for usage. The agent must infer usage based on the purpose alone, which is insufficient for optimal tool selection.

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

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