Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_geometry_nodes

Inspect, configure, or evaluate Geometry Nodes modifier stacks, node trees, links, and interface sockets on a Blender mesh object to build and adjust procedural geometry.

Instructions

Inspects, configures, or evaluates Geometry Nodes modifier stacks, node trees, links, and interface sockets on a scene mesh object.

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": {
      "name": "<name>"
    },
    "name": "configure_geometry_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget object name.
linksNoList of link specifications for configure_graph/update_graph.
nodesNoList of node specifications for configure_graph/update_graph.
valueNoValue to set for set_node_input.
actionNoAction: 'inspect', 'create', 'assign_group', 'add_node', 'remove_node', 'add_link', 'remove_link', 'set_node_input', 'add_socket', 'set_socket_default', 'configure_graph', 'update_graph', 'evaluate', or 'apply'. Defaults to 'inspect'.inspect
in_outNoInterface socket direction for add_socket. Defaults to 'INPUT'.
inputsNoOptional dictionary of initial input socket default values for add_node.
task_idNoOptional task or workflow identifier.
to_nodeNoTarget node name for add_link or remove_link (e.g. 'Output', 'Group Output', or node name).
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoOptional [x, y] coordinates for add_node.
from_nodeNoSource node name for add_link or remove_link (e.g. 'Input', 'Group Input', or node name).
max_valueNoOptional maximum value limit for numeric sockets.
min_valueNoOptional minimum value limit for numeric sockets.
node_nameNoName of node for add_node, remove_node, or set_node_input.
node_typeNoType of node to add for add_node (e.g. 'GeometryNodeTransform', 'GeometryNodeSubdivisionSurface', 'GeometryNodeMeshCube', etc.).
to_socketNoTarget socket name for add_link or remove_link (e.g. 'Geometry', 'Mesh').
parametersNoList of interface parameter specifications for configure_graph/update_graph.
from_socketNoSource socket name for add_link or remove_link (e.g. 'Geometry', 'Mesh').
object_nameNoAlias for name.
socket_nameNoInterface socket name to add or configure.
socket_typeNoSocket type: 'NodeSocketFloat', 'NodeSocketInt', 'NodeSocketVector', 'NodeSocketColor', 'NodeSocketBool', 'NodeSocketString', 'NodeSocketGeometry'.NodeSocketFloat
default_valueNoDefault value for the interface socket.
modifier_nameNoName of the Geometry Nodes modifier. Defaults to 'GeometryNodes'.GeometryNodes
target_objectNoAlias for name.
node_group_nameNoName of the GeometryNodeTree node group to assign or create.
expected_snapshot_idNoOptimistic concurrency state fingerprint from previous inspect call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it never says that actions like remove_node, apply, or update_graph mutate and may destroy existing node-tree state. It also omits the optimistic-concurrency contract implied by expected_snapshot_id and whether 'apply' persists to the .blend file.

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?

A single front-loaded sentence with no filler or repetition. Its brevity is efficient, though it borders on under-specification for a 14-action tool.

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?

For a 27-parameter, 14-action mutation tool with no annotations and no output schema, one sentence is far too thin. It names the domains touched but not the action model, required permissions, return shape, or the concurrency workflow, leaving the agent to reconstruct behavior from parameter names.

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

Parameters3/5

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

Schema description coverage is 100%, so every one of the 27 parameters is already documented in the schema, and the description adds no syntax or format detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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?

States specific verbs and resources: 'Inspects, configures, or evaluates Geometry Nodes modifier stacks, node trees, links, and interface sockets on a scene mesh object.' The scope is concrete, but it does not differentiate itself from the sibling inspect_geometry_nodes despite claiming an 'inspect' mode.

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 tool versus inspect_geometry_nodes or the other node-graph siblings, and no guidance on when to pick 'inspect' versus 'configure_graph'/'update_graph'/'evaluate'/'apply'. The agent must infer the whole routing decision from the enum in the schema.

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