Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_comp_node_input

Idempotent

Set a specific input value on a Blender compositor node, updating node parameters directly.

Instructions

Set a compositor node input value.

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": {
      "node": "<node>",
      "input": "<input>",
      "value": "<value>"
    },
    "name": "set_comp_node_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
inputYes
valueYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The only annotation is idempotentHint, which is already structured. The description adds no behavioral context such as side effects, dependencies (e.g., compositor must be enabled), or error conditions. It fails to go beyond the annotation.

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?

The description is a single, concise sentence with no fluff. However, its brevity borders on under-specification, which limits its utility despite being well-structured.

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?

With no parameter descriptions, no output schema insight, and a simple setter that operates on a specific node tree, the description is incomplete. It lacks context about how the node tree is accessed or how inputs are referenced, making the tool risky to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does not explain how to specify 'node', 'input', or 'value'—no node naming convention, input index vs. name, value types, or units. The agent is left without essential parameter guidance.

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?

The description uses a specific verb ('Set') and resource ('compositor node input'), clearly distinguishing it from shader or geometry node setters. It unambiguously states the tool's function.

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 provides no guidance on when to use this tool versus alternatives like set_node_input or set_geonode_input. It simply states what it does without mentioning prerequisites, contexts, or exclusions.

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