Skip to main content
Glama

get_polyhaven_status

Check if PolyHaven integration is enabled in Blender to determine availability of PolyHaven features for 3D asset generation.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler for the 'get_polyhaven_status' MCP tool. Decorated with @mcp.tool() for registration. It queries the Blender addon socket connection to retrieve the PolyHaven integration status and returns the corresponding message.
    @mcp.tool()
    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", "")
    
            return message
        except Exception as e:
            logger.error(f"Error checking PolyHaven status: {str(e)}")
            return f"Error checking PolyHaven status: {str(e)}"
  • The asset_creation_strategy prompt template that instructs usage of get_polyhaven_status() as the first step to check PolyHaven availability before proceeding with asset creation tools.
    def asset_creation_strategy() -> str:
        """Defines the preferred strategy for creating assets in Blender"""
        return """When creating 3D content in Blender, always start by checking if PolyHaven is available:
    
        0. Before anything, always check the scene from get_scene_info()
        1. First use get_polyhaven_status() to verify if PolyHaven integration is enabled.
    
        2. If PolyHaven is enabled:
           - For objects/models: Use download_polyhaven_asset() with asset_type="models"
           - For materials/textures: Use download_polyhaven_asset() with asset_type="textures"
           - For environment lighting: Use download_polyhaven_asset() with asset_type="hdris"
    
        3. If PolyHaven is disabled or when falling back to basic tools:
           - create_object() for basic primitives (CUBE, SPHERE, CYLINDER, etc.)
           - set_material() for basic colors and materials
    
        Only fall back to basic creation tools when:
        - PolyHaven is disabled
        - A simple primitive is explicitly requested
        - No suitable PolyHaven asset exists
        - The task specifically requires a basic material/color
        """
  • In get_blender_connection(), a call to Blender's get_polyhaven_status command (note: not the MCP tool) to update the global _polyhaven_enabled flag for internal use by other tools.
    _tripo_apikey = result.get("api_key", "")
    result = _blender_connection.send_command("get_polyhaven_status")
    # Store the PolyHaven status globally
    _polyhaven_enabled = result.get("enabled", False)
  • src/server.py:675-675 (registration)
    The @mcp.tool() decorator registers the get_polyhaven_status function as an MCP tool.
    @mcp.tool()
Behavior2/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 states the tool returns a message about feature availability, which implies a read-only operation, but doesn't clarify if it requires specific permissions, has side effects, or details the message format. For a status-checking tool, this is a minimal but incomplete disclosure.

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, using two sentences that directly state the action and outcome without any fluff. Every sentence earns its place by contributing essential information, making it highly efficient.

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, simple status check), the description is adequate but has gaps. It lacks usage guidelines and behavioral details, though the presence of an output schema means it doesn't need to explain return values. For a basic tool, this is minimally viable but could be more informative.

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, focusing instead on the tool's function. This meets the baseline for tools with no parameters, as it avoids unnecessary detail.

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 with a specific verb ('Check') and resource ('PolyHaven integration in Blender'), and distinguishes it from siblings by focusing on status checking rather than asset operations like 'download_polyhaven_asset' or 'search_polyhaven_assets'. However, it doesn't explicitly differentiate from other status-checking tools like 'get_task_status', which slightly reduces specificity.

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., whether Blender must be running), context for checking integration status, or when to choose this over other tools like 'get_task_status' for monitoring. This leaves usage entirely implicit.

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/VAST-AI-Research/tripo-mcp'

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