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()

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 disclosing behavior. It states that the tool returns a message indicating availability, which is transparent for a simple status check. It does not explicitly say 'non-destructive' or 'read-only', but the name and wording imply that, and the return behavior is disclosed.

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 two sentences, front-loaded with the action, and contains no waste. Every word contributes to understanding the tool's purpose and output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no parameters and an output schema present, the description is complete. It clearly states what the tool checks and what it returns, which is all an agent needs to select and invoke it appropriately.

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 zero parameters, so the baseline score is 4. The description does not need to explain parameter meanings, and the empty input schema confirms no parameters are required.

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 the tool's function: checking if PolyHaven integration is enabled in Blender. It uses a specific verb ('Check') and resource ('PolyHaven integration'), and the added return message detail ('Returns a message indicating whether PolyHaven features are available') makes the purpose unambiguous and distinct from sibling tools like get_polyhaven_categories or search_polyhaven_assets.

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

Usage Guidelines3/5

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

The description implies usage context (a status check before using PolyHaven features) but provides no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. It is clear what the tool does, but not explicitly when to invoke it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.