Skip to main content
Glama
Eminemminem

BlenderMCP

by Eminemminem

set_texture

Apply downloaded Polyhaven textures to 3D objects in Blender to enhance visual appearance and material properties.

Instructions

Apply a previously downloaded Polyhaven texture to an object.

Parameters:

  • object_name: Name of the object to apply the texture to

  • texture_id: ID of the Polyhaven texture to apply (must be downloaded first)

Returns a message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_nameYes
texture_idYes

Implementation Reference

  • MCP tool handler for 'set_texture'. Applies a Polyhaven texture to a Blender object by sending a command to the Blender addon. Includes input validation via type hints and docstring, error handling, and detailed response formatting.
    @mcp.tool()
    def set_texture(
        ctx: Context,
        object_name: str,
        texture_id: str
    ) -> str:
        """
        Apply a previously downloaded Polyhaven texture to an object.
        
        Parameters:
        - object_name: Name of the object to apply the texture to
        - texture_id: ID of the Polyhaven texture to apply (must be downloaded first)
        
        Returns a message indicating success or failure.
        """
        try:
            # Get the global connection
            blender = get_blender_connection()
            result = blender.send_command("set_texture", {
                "object_name": object_name,
                "texture_id": texture_id
            })
            
            if "error" in result:
                return f"Error: {result['error']}"
            
            if result.get("success"):
                material_name = result.get("material", "")
                maps = ", ".join(result.get("maps", []))
                
                # Add detailed material info
                material_info = result.get("material_info", {})
                node_count = material_info.get("node_count", 0)
                has_nodes = material_info.get("has_nodes", False)
                texture_nodes = material_info.get("texture_nodes", [])
                
                output = f"Successfully applied texture '{texture_id}' to {object_name}.\n"
                output += f"Using material '{material_name}' with maps: {maps}.\n\n"
                output += f"Material has nodes: {has_nodes}\n"
                output += f"Total node count: {node_count}\n\n"
                
                if texture_nodes:
                    output += "Texture nodes:\n"
                    for node in texture_nodes:
                        output += f"- {node['name']} using image: {node['image']}\n"
                        if node['connections']:
                            output += "  Connections:\n"
                            for conn in node['connections']:
                                output += f"    {conn}\n"
                else:
                    output += "No texture nodes found in the material.\n"
                
                return output
            else:
                return f"Failed to apply texture: {result.get('message', 'Unknown error')}"
        except Exception as e:
            logger.error(f"Error applying texture: {str(e)}")
            return f"Error applying texture: {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 of behavioral disclosure. It mentions the prerequisite (texture must be downloaded first) and the return value (success/failure message), which adds useful context. However, it lacks details on permissions, error conditions, or side effects, leaving gaps for a mutation tool.

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 appropriately sized and front-loaded, with a clear purpose statement followed by parameter explanations and return information. Every sentence adds value without redundancy, making it efficient and easy to parse.

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?

Given the tool's complexity (mutation with prerequisites), no annotations, and no output schema, the description is fairly complete. It covers purpose, parameters, prerequisites, and return indication. However, it could improve by detailing error cases or integration with sibling tools, leaving minor gaps in contextual guidance.

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 description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that object_name is 'Name of the object to apply the texture to' and texture_id is 'ID of the Polyhaven texture to apply (must be downloaded first)', clarifying purpose and constraints. This compensates well for the low schema coverage, though it doesn't detail format or validation rules.

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 specific action ('Apply a previously downloaded Polyhaven texture') and resource ('to an object'), distinguishing it from sibling tools like download_polyhaven_asset or get_object_info. It explicitly mentions the source (Polyhaven) and prerequisite (must be downloaded first), making the purpose unambiguous.

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?

The description provides clear context by specifying that the texture must be 'previously downloaded' and from 'Polyhaven', which implicitly guides usage. However, it does not explicitly state when to use this tool versus alternatives like download_polyhaven_asset or import_generated_asset, nor does it mention exclusions or prerequisites beyond the download requirement.

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

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