Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_shader_nodes

Create, connect, and modify shader nodes for Blender materials and world environments, including removing nodes, setting socket properties, and listing existing node networks.

Instructions

Manipulate shader node graphs for materials or world environments. Supports creating nodes, removing nodes, connecting sockets, disconnecting sockets, setting socket/node properties, and listing existing node networks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_name": "<target_name>"
    },
    "name": "manage_shader_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoNode graph action to perform.create_node
task_idNoOptional task or workflow identifier.
to_nodeNoDestination node name for connection/disconnection.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoOptional [x, y] coordinates in the Node Editor canvas.
from_nodeNoSource node name for connection/disconnection.
node_nameNoName or identifier of the node for creation, removal, or property updates.
node_typeNoBlender shader node RNA type (e.g., ShaderNodeTexImage, ShaderNodeMapping, ShaderNodeTexCoord, ShaderNodeMath).
to_socketNoDestination input socket name or index.
from_socketNoSource output socket name or index.
target_nameYesName of the target Material or World datablock.
target_typeNoTarget datablock type (MATERIAL or WORLD). Defaults to MATERIAL.MATERIAL
property_nameNoProperty or input socket name when action is set_property.
property_valueNoValue to assign when action is set_property (scalar, string, or array).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it omits that create/remove/connect/set_property are mutating and that remove_node/detach operations are destructive and un-undoable. It says nothing about required state (an existing material or world datablock, active object), permission/consent requirements, or what happens when a named node or socket does not exist.

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?

Two sentences, front-loaded with the verb and resource, then a compact capability enumeration that mirrors the action enum. No filler, though the enumeration partly restates what the enum already conveys.

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?

For a 14-parameter mutation tool with no annotations and no output schema, the description leaves too much unexplained: action-specific parameter requirements, the untrusted/deprecated status of 'approved', value typing for property_value, and return behavior are all absent.

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 coverage is 100%, so every parameter is already documented in the schema, including the action enum values and the deprecated 'approved' flag. The description adds only the high-level capability list and no extra meaning about which parameters each action requires (e.g. from_node/to_socket for connect, property_name/property_value for set_property).

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?

States a specific verb and resource ('Manipulate shader node graphs for materials or world environments') and enumerates the exact six operations, which map directly to the action enum. An agent can distinguish this from compositor/geometry node tools by the explicit 'shader node graph' scoping.

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 lists capabilities but gives no when-to-use guidance, no prerequisites, and no exclusions. It never addresses the overlapping sibling connect_shader_nodes, nor does it say which action to prefer or when a dedicated tool like configure_material_shader is more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools