Skip to main content
Glama
iflow-mcp

BlenderMCP

by iflow-mcp
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_polyhaven_status

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

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

  • src/blender_mcp/server.py:526-540 (handler)
    The `get_polyhaven_status` tool handler that checks PolyHaven integration status via the blender connection.
    @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:

Tool Definition Quality

A4/5.0
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 discloses that the tool returns a message indicating availability status, which covers the basic behavioral contract. However, it lacks details on the return format, specific states (enabled/disabled), or error conditions.

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 consists of two efficient sentences with zero waste. It is properly front-loaded with the action ('Check') first, followed by the return value description. Every sentence earns its place.

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 simple status-checking tool with no parameters and no output schema, the description adequately explains what the tool does and what it returns. While it could specify the exact return value structure or format, the semantic explanation ('message indicating whether...available') is sufficient for agent decision-making.

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 and 100% schema description coverage trivially. The baseline score of 4 applies as there are no parameters requiring semantic clarification beyond the schema.

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 a specific verb 'Check' with the specific resource 'PolyHaven integration in Blender', clearly distinguishing it from sibling tools like download_polyhaven_asset, search_polyhaven_assets, and get_polyhaven_categories which perform actions rather than status checks.

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 by stating it returns whether features are available, suggesting it should be called before using other PolyHaven features. However, it lacks explicit guidance such as 'Call this before using download_polyhaven_asset' or specific prerequisites.

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

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