Skip to main content
Glama

add_geometry_node

Adds a node of a specified type to an existing geometry node group, enabling procedural modeling and AI-driven Blender workflows.

Instructions

Add a node to a geometry node group.

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": {
      "group_name": "<group_name>",
      "node_type": "<node_type>"
    },
    "name": "add_geometry_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_nameNo
node_typeYes
group_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing beyond implying a mutation. It does not state whether group_name must reference an existing group, whether an invalid node_type raises an error, whether node_name defaults to the type name (schema shows a null default), or whether duplicate names are permitted. For a write operation with zero annotation coverage, this is a significant gap.

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 front-loaded sentence with zero padding — nothing is wasted. However, the brevity here reflects under-specification rather than disciplined economy, so it stops short of a 5.

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?

Because an output schema exists, return values need not be described, which relieves some burden. Still, for a mutating, three-parameter tool with no annotations and 0% schema coverage, the description omits prerequisites, defaults, and failure modes that an agent needs to call it correctly.

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% across three parameters, so the description must compensate and does not: node_type, group_name, and especially the optional node_name (what happens if it is null) are never explained. The words 'node' and 'node group' loosely echo node_type and group_name, but node_name receives no treatment at all.

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 uses a specific verb+resource pair ('Add a node to a geometry node group') that clearly identifies a creation operation scoped to a node group. It implicitly distinguishes itself from siblings like connect_geometry_nodes and set_geometry_node_input, though it never names an alternative. A clear purpose, but no explicit sibling differentiation.

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 guidance on when to use this versus connect_geometry_nodes, create_node_group, or set_geometry_node_input, and no prerequisites stated. The agent must infer from the sibling list that list_geometry_node_types is the place to discover valid node_type values and that a group must already exist.

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