Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_nodes

Manipulate Blender shader node graphs for materials or worlds: create or remove nodes, connect or disconnect sockets, set properties, and list 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_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

C2.9/5.0
Behavior2/5

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

No annotations are provided. The description only says 'manipulate' and lists operations; it does not disclose that remove_node is destructive, whether changes are reversible, what permissions or context are needed, or how material/world target selection affects behavior.

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?

Two sentences, front-loaded with the resource and scope, followed by a compact action list. No redundant or filler text.

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/query tool with no annotations and no output schema, the description is too thin: it omits safety profile, prerequisites, return/result behavior, and parameter interaction guidance.

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 all 14 parameters are already documented in the schema. The description mentions the action categories but adds no extra meaning about parameter interactions, such as using node_name vs from_node/to_node, or 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (shader node graphs for materials or world environments) and lists operations, so the agent understands it is a mutation/query tool for shader nodes. However, it does not differentiate from sibling tools such as manage_shader_nodes or connect_shader_nodes, leaving overlap unresolved.

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 action list implies the tool can be used for create/remove/connect/disconnect/set/list operations, but there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives like manage_shader_nodes or connect_shader_nodes despite many siblings.

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