Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_geometry_nodes

Inspect, configure, and evaluate Geometry Nodes modifier stacks, node trees, links, and interface sockets on Blender mesh objects for procedural modeling workflows.

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": "inspect_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 provided, so the description must carry the behavioral burden for a 27-parameter, mutation-capable tool. It does not disclose read-only versus write behavior, side effects, permission requirements, or the optimistic-concurrency mechanism hinted at by expected_snapshot_id, leaving safety and mutation semantics undocumented.

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?

It is a single front-loaded sentence with no filler, and the resource scope appears immediately. The sentence is dense but efficient; its main weakness is underspecification, which is better captured under contextual completeness than conciseness.

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 highly complex tool with 27 parameters, multiple actions, nested objects, no annotations, and no output schema, a single sentence is not sufficient. It omits action-specific prerequisites, mutation/read distinctions, concurrency usage, and return behavior, so an agent cannot fully predict how to call it correctly.

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 the input schema already explains all 27 parameters, including action enums and aliases. The description adds no parameter-level meaning beyond naming the resource categories, so the baseline 3 is appropriate.

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 names a specific resource—Geometry Nodes modifier stacks, node trees, links, and interface sockets—on a scene mesh object. However, it bundles three verbs ('inspects, configures, or evaluates') and does not distinguish the read-oriented name from the separate configure_geometry_nodes sibling, so the primary purpose is clear but not sharply differentiated.

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 configure_geometry_nodes, inspect_modifier_stack, or the other node-management siblings, and no conditions or exclusions are stated. The action enum in the schema supplies operational choices, but the description itself leaves selection entirely to inference.

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