Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_compositor

Create, connect, inspect, and adjust Blender compositor nodes to apply post-processing effects such as 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": "configure_compositor"
  }
}

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 provided, so the description carries the full burden of behavioral disclosure for a mutating tool with destructive actions (remove_node, disconnect, set_property). It says nothing about reversibility, whether changes persist to the .blend, side effects on existing node graphs, or the meaning of the connection/snapshot machinery implied by the schema.

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?

A single front-loaded sentence with no filler; the resource is stated before the use-case list. It is efficient, though the effect list partially duplicates schema examples rather than clarifying the multi-action model.

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 tool with no annotations and no output schema, yet the description never explains how actions map to parameters, what 'inspect' returns, or what a successful mutation looks like. For a surface this broad, the single sentence leaves major gaps an agent must guess at.

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%, so the schema already documents all 16 parameters including the action enum, node types, sockets, and passes dictionary. The description adds no parameter-level meaning beyond echoing effect categories, so 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-plus-resource ('Manipulate Blender's compositing node tree') and enumerates concrete domains (bloom/glare, denoising, color grading, render passes, composite outputs). However, 'manipulate' is vague against the actual 9-action surface (enable, create_node, remove_node, connect, disconnect, set_property, configure_render_passes, list_nodes, inspect), and it never distinguishes itself from siblings such as manage_compositor_nodes or inspect_compositor_pipeline.

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 when-to-use guidance, no prerequisites, and no alternatives named despite obvious overlapping siblings (inspect_compositor_pipeline, manage_compositor, manage_compositor_nodes). The 'inspect' and 'list_nodes' actions plausibly collide with inspect_compositor_pipeline, and the description offers nothing to disambiguate them.

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