Skip to main content
Glama

search_polyhaven_assets

Find 3D assets on Polyhaven for Blender projects. Filter by asset type and categories to locate HDRI environments, textures, or models.

Instructions

Search for assets on Polyhaven with optional filtering.

Parameters:

  • asset_type: Type of assets to search for (hdris, textures, models, all)

  • categories: Optional comma-separated list of categories to filter by

Returns a list of matching assets with basic information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_typeNoall
categoriesNo

Implementation Reference

  • The handler function for the 'search_polyhaven_assets' MCP tool. It connects to Blender, sends a 'search_polyhaven_assets' command with parameters, processes the response by sorting assets by popularity, and formats a readable output listing the assets with their details.
    @mcp.tool()
    def search_polyhaven_assets(
        ctx: Context,
        asset_type: str = "all",
        categories: str = None
    ) -> str:
        """
        Search for assets on Polyhaven with optional filtering.
        
        Parameters:
        - asset_type: Type of assets to search for (hdris, textures, models, all)
        - categories: Optional comma-separated list of categories to filter by
        
        Returns a list of matching assets with basic information.
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("search_polyhaven_assets", {
                "asset_type": asset_type,
                "categories": categories
            })
            
            if "error" in result:
                return f"Error: {result['error']}"
            
            # Format the assets in a more readable way
            assets = result["assets"]
            total_count = result["total_count"]
            returned_count = result["returned_count"]
            
            formatted_output = f"Found {total_count} assets"
            if categories:
                formatted_output += f" in categories: {categories}"
            formatted_output += f"\nShowing {returned_count} assets:\n\n"
            
            # Sort assets by download count (popularity)
            sorted_assets = sorted(assets.items(), key=lambda x: x[1].get("download_count", 0), reverse=True)
            
            for asset_id, asset_data in sorted_assets:
                formatted_output += f"- {asset_data.get('name', asset_id)} (ID: {asset_id})\n"
                formatted_output += f"  Type: {['HDRI', 'Texture', 'Model'][asset_data.get('type', 0)]}\n"
                formatted_output += f"  Categories: {', '.join(asset_data.get('categories', []))}\n"
                formatted_output += f"  Downloads: {asset_data.get('download_count', 'Unknown')}\n\n"
            
            return formatted_output
        except Exception as e:
            logger.error(f"Error searching Polyhaven assets: {str(e)}")
            return f"Error searching Polyhaven assets: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'optional filtering' and 'returns a list of matching assets with basic information,' which gives some context about output format. However, it lacks details on rate limits, authentication needs, pagination, error handling, or what 'basic information' entails, leaving significant gaps for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: the first sentence states the core purpose, followed by a bulleted list of parameters and a note on returns. There's no wasted text, and the structure aids readability. A perfect score would require even tighter phrasing or more strategic emphasis.

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

Completeness2/5

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

Given the complexity (a search tool with filtering), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the return structure (e.g., what fields are in 'basic information'), error cases, or how results are ordered/limited. For a tool with 2 parameters and no structured output, more context is needed to guide the agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal semantics beyond the input schema. It explains that 'asset_type' filters by type (e.g., hdris, textures) and 'categories' is an optional comma-separated list for filtering, which clarifies usage. However, with 0% schema description coverage, it doesn't fully compensate—e.g., it doesn't specify valid categories or format details. The baseline is 3 due to some added value, but it's incomplete.

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: 'Search for assets on Polyhaven with optional filtering.' It specifies the verb ('search'), resource ('assets on Polyhaven'), and scope ('with optional filtering'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_polyhaven_categories' or 'download_polyhaven_asset', which would be needed for a perfect score.

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 sibling tools like 'get_polyhaven_categories' (which might provide metadata) or 'download_polyhaven_asset' (which retrieves specific assets), nor does it specify prerequisites or exclusions. The agent must infer usage from the purpose alone.

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/spranjal3301/final-year-project'

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