Skip to main content
Glama

blender_geonodes

Create and manage geometry node groups for procedural modeling in Blender. Add nodes, connect them, and assign modifiers to objects.

Instructions

Geometry Nodes graph operations (procedural modeling).

Operations:

  • create_group: create or reuse a GeometryNodeTree

  • add_node: add a node to the group

  • connect_nodes: wire two nodes in the group

  • assign_modifier: attach node group to an object as Geometry Nodes modifier

  • add_input: expose a group input socket

  • list_node_types: common GeometryNode types for agents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNocreate_group
group_nameNoGeoNodes
object_nameNo
node_typeNoGeometryNodeMeshCube
node_nameNo
from_nodeNo
from_socketNo
to_nodeNo
to_socketNo
modifier_nameNo
location_xNo
location_yNo
input_nameNoInput
socket_typeNoNodeSocketFloat
default_valueNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as side effects, permission requirements, or whether operations are destructive. The list of operations implies mutations but no explicit safety info.

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?

Description is short and front-loaded with purpose. Bullet list of operations is clear, though could be more structured. No unnecessary sentences.

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

Completeness1/5

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

Given 15 undocumented parameters and an output schema not described, the description is insufficient for an agent to use the tool correctly. Critical details for parameter usage and return values are missing.

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?

With 0% schema description coverage and 15 parameters, the description fails to explain parameter meanings or how they map to operations. For example, 'node_type' defaulting to 'GeometryNodeMeshCube' is unexplained.

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?

Description clearly states 'Geometry Nodes graph operations (procedural modeling)' and lists specific sub-operations, distinguishing it from sibling tools like blender_mesh or blender_modifiers.

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?

No guidance on when to use this tool vs alternatives, no prerequisites or when-not-to-use instructions. The description only lists operations without context.

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/sandraschi/blender-mcp'

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