Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_compositor_nodes

Create, connect, inspect, and configure Blender compositor nodes to apply bloom, denoising, color grading, render passes, and composite outputs.

Instructions

Manipulate Blender's compositing node tree for post-processing effects, bloom/glare, denoising, color grading, render passes, and composite outputs in Blender 5.2.2 LTS.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "manage_compositor_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoCompositing action to perform.inspect
inputsNoOptional initial socket values for node creation.
passesNoDictionary of pass names to booleans for configure_render_passes (e.g. {'z': true, 'normal': true, 'diffuse': true, 'glossy': true, 'ao': true, 'shadow': true, 'emission': true, 'environment': true, 'mist': true}).
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] node placement coordinates.
from_nodeNoSource node name for connection/disconnection.
node_nameNoName or identifier of the node for creation, removal, or property updates.
node_typeNoCompositor node type (e.g. CompositorNodeGlare, CompositorNodeDenoise, CompositorNodeBlur, CompositorNodeColorBalance, CompositorNodeCryptomatteV2).
to_socketNoDestination input socket name or index.
scene_nameNoOptional scene name (defaults to active scene).
from_socketNoSource output socket name or index.
property_nameNoProperty name when action is set_property.
property_valueNoValue to assign when action is set_property.
expected_snapshot_idNoOptional snapshot identifier for optimistic concurrency control (stale-state protection).

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 supplied, so the description carries the full behavioral burden, yet it discloses nothing about mutation semantics. It never says that actions like remove_node, disconnect, or set_property alter scene state, whether changes are undoable, what permissions or Blender connection state is required, or what the expected_snapshot_id / deprecated 'approved' flags mean for concurrency and consent.

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?

One compact sentence with the resource and scope front-loaded and no filler. The version string 'Blender 5.2.2 LTS' is of questionable value, but it is brief and does not obscure the core statement.

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?

This is a 16-parameter, 9-action mutation tool with no annotations and no output schema, yet the description never enumerates the actions or explains how they map to the parameter groups (from_node/to_node for connect, passes for configure_render_passes, property_name/property_value for set_property). It lists use-case categories instead of the operational surface an agent must choose from.

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% across all 16 parameters, so the schema already documents sockets, node types, passes, and placement. The description adds no parameter-level meaning beyond echoing the domain vocabulary (glare, denoise, render passes), so the baseline 3 applies.

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 names a specific verb and resource — 'Manipulate Blender's compositing node tree' — and scopes it with concrete effect categories (bloom/glare, denoising, color grading, render passes). It does not, however, distinguish itself from very close siblings such as manage_compositor, configure_compositor, manage_nodes, or inspect_compositor_pipeline, which is a real ambiguity given four similarly named compositor tools.

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?

There is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives. The only signal is the enumerated effect types, which merely imply the domain rather than telling an agent which tool to pick for a given task.

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