Skip to main content
Glama
ZachHandley

blender-mcp-enhanced

by ZachHandley

complete_geometry_node

Construct a geometry node network for procedural modeling. Define nodes, links, and inputs to create parametric objects like tables or organic shapes.

Instructions

Create a complete geometry node network for procedural modeling.

This tool enables AI-driven procedural modeling by creating sophisticated geometry node networks.
Perfect for creating parametric objects like tables, chairs, organic shapes, and complex procedural geometry.

Parameters:
- object_name: Name of the object to apply geometry nodes to (will be created if doesn't exist)
- nodes: List of node definitions, each containing:
  - type: Node type (e.g., "GeometryNodeMeshCube", "GeometryNodeSubdivisionSurface")
  - location: [x, y] position in node editor (optional)
  - label: Custom label for the node (optional)
  - inputs: Dict of input values {input_name: value} (optional)
  - properties: Dict of node properties {property_name: value} (optional)
- links: List of connections between nodes:
  - from_node: Source node index (int) or name (str)
  - from_socket: Source socket name (str) or index (int)
  - to_node: Target node index (int) or name (str)
  - to_socket: Target socket name (str) or index (int)
- input_sockets: Interface inputs for the node group (optional):
  - name: Input name
  - type: Socket type (e.g., "VALUE", "VECTOR", "GEOMETRY")
  - value: Default value (optional)

Example for a simple procedural table:
nodes = [
    {"type": "NodeGroupInput", "location": [0, 0]},
    {"type": "GeometryNodeMeshCube", "location": [200, 200], "inputs": {"Size": [2, 0.1, 1]}},
    {"type": "GeometryNodeMeshCube", "location": [200, 0], "inputs": {"Size": [0.1, 1.8, 0.1]}},
    {"type": "GeometryNodeJoinGeometry", "location": [400, 100]},
    {"type": "NodeGroupOutput", "location": [600, 100]}
]
links = [
    {"from_node": 1, "from_socket": "Mesh", "to_node": 3, "to_socket": 0},
    {"from_node": 2, "from_socket": "Mesh", "to_node": 3, "to_socket": 0},
    {"from_node": 3, "from_socket": "Geometry", "to_node": 4, "to_socket": "Geometry"}
]

Returns success message with details about the created node network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksYes
nodesYes
object_nameYes
input_socketsNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions that the object will be created if it doesn't exist and returns a success message, but lacks details on side effects, error conditions, or any destructive actions that might occur.

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 well-structured with a brief overview, parameter details, and a concrete example. However, it is somewhat lengthy and could be more concise by shortening the example or removing redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, nested objects) and lack of output schema, the description covers the main aspects including parameter explanations and a complete example. It lacks mention of error handling, limitations, or behavior when object already exists, but is still fairly complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully explains each parameter with detailed structure: object_name, nodes (with subfields), links, and input_sockets. An example demonstrates usage, adding significant value beyond the schema.

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 clearly states 'Create a complete geometry node network for procedural modeling' with specific verb (create) and resource (geometry node network). It distinguishes from sibling tools like get_geometry_nodes_status and clear_context_scripts, which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by saying 'Perfect for creating parametric objects...' but lacks explicit guidance on when to use this tool versus alternatives, and does not mention when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZachHandley/blender-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server