Skip to main content
Glama

set_texture

Apply downloaded Polyhaven textures to 3D objects in Blender using texture IDs and object names for visual 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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'set_texture' MCP tool. It is decorated with @mcp.tool() for automatic registration. The function connects to Blender, sends the 'set_texture' command with object_name and texture_id parameters, processes the result, and returns a detailed success message including material information and node details, or an error message.
    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?

No annotations are provided, so the description carries full burden. It mentions 'Apply' (implying mutation) and a prerequisite ('must be downloaded first'), but doesn't disclose behavioral traits like permissions needed, whether changes are reversible, error handling, or rate limits. 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.

Conciseness4/5

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

The description is appropriately sized with three sentences: purpose, parameters, and return value. It's front-loaded with the main action, and each sentence adds value (e.g., the parameter list clarifies inputs). Minor room for improvement in flow, but overall efficient.

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 2 parameters, no annotations, and an output schema (implied by 'Returns a message'), the description is fairly complete: it covers purpose, parameters with semantics, and return indication. However, it could better address behavioral aspects like error cases or integration with sibling tools, keeping it from a 5.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining '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)', which clarifies purpose and constraints. However, it doesn't detail format or examples, leaving some ambiguity.

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 target ('a previously downloaded Polyhaven texture to an object'), distinguishing it from siblings like 'set_material' or 'modify_object' by specifying texture application. However, it doesn't explicitly differentiate from all siblings (e.g., 'modify_object' might also handle textures), keeping it at 4 rather than 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 noting the texture 'must be downloaded first' (referencing 'download_polyhaven_asset'), but it doesn't explicitly state when to use this tool versus alternatives like 'set_material' or provide exclusions. This gives some context but lacks clear guidance on tool selection.

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/VAST-AI-Research/tripo-mcp'

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