Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_node_group

Create a node group from selected nodes in Blender, organizing material node networks into reusable groups.

Instructions

Create a node group from selected nodes.

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": {
      "material": "<material>",
      "nodes": "<nodes>"
    },
    "name": "create_node_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNodeGroup
nodesYes
materialYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It states 'Create' implying mutation, but does not explain side effects, prerequisites, or what happens to the original nodes. It also leaves 'selected nodes' undefined.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is one short, front-loaded sentence with no filler words. However, it is under-specified for a tool with 3 parameters, so the brevity comes at the cost of essential context.

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?

Despite having an output schema, the description is incomplete for a mutation tool. It does not clarify the role of 'material', the meaning of 'selected nodes', or how this tool relates to node editing workflows. Insufficient guidance for correct usage.

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%, and the description fails to explain any parameters. 'material' is required but not mentioned in the description, and 'nodes' is only vaguely hinted at as 'selected nodes'. The agent cannot determine the meaning or format of these parameters from the description.

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 verb 'Create' and resource 'node group' clearly define the action, and 'from selected nodes' indicates the input. It distinguishes itself from sibling tools like create_shader_node and create_geonode by operating on a group level, though it doesn't specify which node tree type.

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?

Provides no guidance on when to use this tool versus alternatives. No mention of prerequisites, such as having nodes selected or a material open in the node editor, nor any comparison with related tools like add_node_group_instance.

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