Skip to main content
Glama

get_polyhaven_status

Check if PolyHaven integration is enabled in Blender to verify availability of its features for 3D modeling and scene manipulation.

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 handler function `get_polyhaven_status` which checks the PolyHaven integration status via the blender connection.
    @telemetry_tool("get_polyhaven_status")
    @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", "")
            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)}")
Behavior3/5

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

With no annotations provided, the description carries the full burden. It appropriately notes the tool returns a message about availability, indicating read-only behavior. However, it omits potential error conditions (e.g., if Blender is not running) or the specific format/content of the returned message.

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 efficient sentences: first defines the action and target, second explains the return value. No redundancy or unnecessary elaboration for this simple status-check tool.

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?

Adequate for a zero-parameter status tool. The description mentions the return message弥补了 the lack of output schema, and specifies the Blender integration context. Could improve by indicating whether the check requires active Blender connection or handles offline states.

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?

Zero parameters exist, establishing a baseline of 4. The description does not need to elaborate on input parameters, and instead appropriately focuses on describing the operation and return value semantics.

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?

Description clearly defines the specific action ('Check') and resource ('PolyHaven integration status in Blender'), distinguishing it from siblings like get_sketchfab_status and download_polyhaven_asset by specifying the PolyHaven domain and read-only status check nature.

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

Usage Guidelines4/5

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

Provides clear context for when to use the tool by stating it 'Returns a message indicating whether PolyHaven features are available,' which implicitly signals to check this before attempting PolyHaven operations. Lacks explicit mention of prerequisite relationships with download_polyhaven_asset or search_polyhaven_assets.

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

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