Skip to main content
Glama
opslon

BlenderMCP

by opslon

set_texture

Apply downloaded Polyhaven textures to objects in Blender to enhance 3D models with realistic surfaces.

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 set_texture tool handler, which communicates with Blender to apply a texture. It is registered with the @mcp.tool() decorator.
    @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
            })
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 that the tool 'Returns a message indicating success or failure,' which adds some context about output behavior. However, it fails to disclose critical traits such as whether this is a destructive operation (modifies the object), any authentication or permission requirements, rate limits, or error handling specifics, which are essential for safe and effective use.

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. Each sentence earns its place, with no redundant information. Minor improvements could include integrating the parameter list more seamlessly, but overall it's efficient.

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 (a mutation tool with 2 parameters), no annotations, and no output schema, the description is moderately complete. It covers the basic purpose, parameters, and return type, but lacks details on behavioral traits, error cases, or integration with sibling tools (e.g., how 'texture_id' relates to 'download_polyhaven_asset'). For a tool that modifies objects, more context on safety and dependencies would be beneficial.

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 schema provides no parameter details. The description compensates by listing both parameters ('object_name' and 'texture_id') with brief explanations, adding meaning beyond the bare schema. However, it doesn't specify formats, constraints, or examples (e.g., what constitutes a valid texture ID), leaving some semantic gaps.

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: 'Apply a previously downloaded Polyhaven texture to an object.' It specifies the verb ('apply'), resource ('Polyhaven texture'), and target ('object'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'import_generated_asset' or 'get_object_info', which could involve similar objects or textures.

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 provides some implied usage guidance by mentioning that the texture 'must be downloaded first,' which references the sibling tool 'download_polyhaven_asset.' However, it lacks explicit when-to-use rules, alternatives, or exclusions compared to other texture-related tools in the list, leaving room for ambiguity in 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/opslon/blender-mcp-optimized'

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