Skip to main content
Glama

set_texture

Apply Polyhaven textures to 3D objects in Blender by specifying the object name and texture ID for material customization.

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

  • The main handler function for the 'set_texture' MCP tool. It takes object_name and texture_id, sends a 'set_texture' command to the Blender connection, and formats the response with details about the applied material and nodes.
    @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)}"
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that the texture must be 'previously downloaded', which adds useful context about prerequisites. However, it fails to disclose critical behavioral traits such as whether this operation is destructive (e.g., overwrites existing textures), requires specific permissions, has rate limits, or what happens on failure beyond a generic 'message'. For a mutation tool with zero annotation coverage, this is a significant gap.

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: the first sentence states the core purpose, followed by a clear parameter list and return information. Every sentence earns its place by adding essential details without redundancy. The structure is logical and easy to parse, making it highly efficient for an AI agent.

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

Completeness3/5

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

Given the complexity of applying textures (a mutation operation), no annotations, no output schema, and 2 parameters, the description is minimally adequate. It covers the purpose, parameters, and a basic return indication, but lacks details on behavioral aspects like error conditions, side effects, or output format. For a tool that modifies state, this leaves gaps that could hinder correct agent invocation, though it meets a baseline level of completeness.

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 explicitly lists both parameters with brief semantics: 'object_name' as 'Name of the object to apply the texture to' and 'texture_id' as 'ID of the Polyhaven texture to apply (must be downloaded first)'. This adds meaningful context beyond the schema, which has 0% description coverage and only provides titles. The constraint on 'texture_id' being downloaded first is particularly valuable. With 2 parameters fully covered in the description, it compensates well for the low schema coverage.

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 action ('Apply') and resources ('previously downloaded Polyhaven texture' to 'an object'), making the purpose understandable. It distinguishes from siblings like 'download_polyhaven_asset' by focusing on application rather than acquisition. However, it doesn't explicitly differentiate from other texture-related tools that might exist, keeping it at 4 instead of 5.

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 the texture 'must be downloaded first', which references the sibling tool 'download_polyhaven_asset'. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'import_generated_asset' or other texture application methods, nor does it mention when not to use it. This leaves usage context somewhat inferred rather than clearly defined.

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/johncarlo177/Python.BlenderMCP'

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