Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

connect_shader_nodes

Connects shader node sockets within a Blender material or world graph, linking a source output to a destination input to build or adjust 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": "connect_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.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does not disclose that remove_node/disconnect are destructive, whether changes are undoable, or what happens on a bad socket name. The schema's "approved" field is flagged DEPRECATED/UNTRUSTED, yet the description is silent on any approval or consent requirement, which is a meaningful omission 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.

Conciseness4/5

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

Two sentences, capability-first, with the operation list compactly packed and no filler. It is somewhat enumeration-heavy and does not front-load which action is the default (create_node).

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?

For a 14-parameter mutation tool with no annotations and no output schema, the description covers the operation surface but omits side-effect, failure, and consent behavior. The rich schema compensates for parameter naming, keeping this at a minimum-viable level rather than inadequate.

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 100%, including a detailed note for node_type (Blender RNA classes) and enums for action and target_type, so the baseline is 3. The description adds only the action-to-operation mapping and no extra syntax or format detail beyond the schema.

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?

States a specific verb and resource ("Manipulate shader node graphs") scoped to materials or world environments, and enumerates the six supported operations, matching the action enum. It never names or contrasts with the nearby siblings manage_shader_nodes or configure_material_shader, so differentiation is left to inference.

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?

Usage is only implied: the action list tells an agent what the tool can do, but there is no statement about when to pick it over manage_shader_nodes, configure_material_shader, or inspect_material_shader. No prerequisites (e.g., that a target material must already exist) are stated.

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