Skip to main content
Glama

create_node_group

Create a geometry node group in Blender to organize and reuse procedural node setups for modeling tasks.

Instructions

Create a geometry node group.

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": "create_node_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden of behavioral disclosure. It does not say whether the group is added to the scene, attached to an object, whether the name defaults/auto-generates, whether duplicate names are rejected, or what side effects occur. Only the bare mutation is implied by the verb.

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?

A single short sentence with the verb and resource front-loaded and zero filler. Nothing is redundant, though the brevity comes at the cost of detail assessed in other dimensions.

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?

An output schema exists, so return values need not be explained. But for a creation tool with no annotations and a 0%-documented parameter, the description leaves too much unstated: scene context, naming behavior, and how the result relates to the sibling inspect/add/set tools that operate on node groups.

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

Parameters2/5

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

Schema description coverage is 0% and there is one optional parameter, 'name', with a null default. The description never mentions the parameter, so an agent gets no guidance on what the name controls, whether it is required for later reference, or how an unnamed group is identified. The description does not compensate for the coverage gap.

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 verb and resource: 'Create a geometry node group.' An agent knows exactly what is produced. It does not, however, distinguish this from near-neighbors like create_geometry_nodes_modifier or inspect_node_group, so the agent must infer the boundary.

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 stated precondition (e.g. whether a scene or object context is required), and no mention of the alternative siblings that also create node-related constructs. The agent is left to infer everything about timing and applicability.

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