Skip to main content
Glama

get_polyhaven_status

Check if PolyHaven integration is enabled in Blender to verify availability of PolyHaven features for asset integration.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_polyhaven_status' tool. It connects to Blender via get_blender_connection(), sends the 'get_polyhaven_status' command, processes the response, and returns a status message indicating if PolyHaven integration is enabled.
    def get_polyhaven_status(ctx: Context) -> str:
        """
        Check if PolyHaven integration is enabled in Blender.
        Returns a message indicating whether PolyHaven features are available.
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_polyhaven_status")
            enabled = result.get("enabled", False)
            message = result.get("message", "")
            if enabled:
                message += "PolyHaven is good at Textures, and has a wider variety of textures than Sketchfab."
            return message
        except Exception as e:
            logger.error(f"Error checking PolyHaven status: {str(e)}")
            return f"Error checking PolyHaven status: {str(e)}"
  • The @mcp.tool() decorator registers the get_polyhaven_status function as an MCP tool.
    def get_polyhaven_status(ctx: Context) -> str:
  • Helper code in get_blender_connection() that calls the underlying Blender 'get_polyhaven_status' command to cache the PolyHaven enabled status.
    # First check if PolyHaven is enabled by sending a ping command
    result = _blender_connection.send_command("get_polyhaven_status")
    # Store the PolyHaven status globally
    _polyhaven_enabled = result.get("enabled", False)
    return _blender_connection
  • Documentation in the asset_creation_strategy prompt recommending the use of get_polyhaven_status() to check PolyHaven status before using related tools.
    Use get_polyhaven_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 states the tool 'Returns a message indicating whether PolyHaven features are available,' which implies a read-only, non-destructive operation, but doesn't specify details like response format, error handling, or performance characteristics. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness5/5

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

The description is extremely concise and front-loaded: two sentences that directly state the tool's purpose and return value. Every word earns its place with no redundancy or fluff, making it easy for an agent to parse quickly.

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 explains what the tool does and what it returns, but lacks details like the message format or integration specifics. With no output schema, the agent might need more context about return values, but the simplicity of the tool keeps it from being incomplete.

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 the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, so it appropriately focuses on the tool's function. A baseline of 4 is applied since no parameters are present, and the description doesn't add unnecessary param details.

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 PolyHaven integration is enabled in Blender.' This specifies the verb ('Check') and resource ('PolyHaven integration in Blender'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_hyper3d_status' or 'get_sketchfab_status' beyond the resource name, which prevents a perfect score.

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 doesn't mention prerequisites (e.g., if Blender must be running), exclusions, or comparisons to similar tools like 'get_hyper3d_status' or 'get_sketchfab_status'. The agent must infer usage from context alone, which is insufficient for clear decision-making.

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

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