BlenderMCP

Overview Schema Source Related Servers Discussions Admin

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

Name	Required	Description	Default
No arguments

Implementation Reference

src/blender_mcp/server.py:527-543 (handler)

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)}"

src/blender_mcp/server.py:527-527 (registration)
The @mcp.tool() decorator registers the get_polyhaven_status function as an MCP tool.
```
def get_polyhaven_status(ctx: Context) -> str:
```

src/blender_mcp/server.py:216-220 (helper)

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

src/blender_mcp/server.py:887-887 (helper)
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
```

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 4, 2026
- addedInput schema / title
```
Added value: +"get_polyhaven_statusArguments"
```
First observedNov 17, 2025

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It states the tool 'returns a message' about feature availability, which implies a read-only status query, but it does not disclose whether it queries Blender state or makes network calls, nor possible errors. The non-mutating nature is inferred from 'Check' rather than stated.

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?

Two short sentences with no filler. The primary action is front-loaded, and the return behavior is separated in the second sentence.

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

Completeness4/5

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

For a zero-parameter status check, the description provides the essential purpose and return information. It lacks an explicit statement of the message format or error behavior, and no output schema compensates, so it is not fully specified.

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 there is nothing to document. The baseline of 4 applies because schema coverage is complete and the description correctly says nothing about parameters.

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 uses the specific verb 'Check' with the resource 'PolyHaven integration in Blender', making the operation immediately clear. It names PolyHaven, distinguishing it from sibling status tools like get_sketchfab_status and get_hyper3d_status.

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 the tool is a capability check but gives no explicit guidance on when to invoke it or when to prefer a sibling status tool. There is no mention of using it before PolyHaven asset operations or an alternative. This is acceptable but relies on inference.

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

Deploy Server