Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_modeling_geometry

Configure a finite, transactional Geometry Nodes setup by specifying typed nodes, parameters, and socket-level links, then read back the evaluated mesh.

Instructions

Finite transactional full Geometry Nodes specification: typed nodes/parameters/links, exact socket identifiers (root semantic names), evaluated mesh readback. No arbitrary nodes or external references. Finite contract verified in disposable Blender 5.2.2; broader domain remains partial.

Input Schema

NameRequiredDescriptionDefault
nameYes
linksYes
nodesYes
actionYes
approvedNo
group_nameYes
parametersNo
modifier_nameYes
expected_snapshot_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose genuinely useful traits: the operation is transactional, the graph domain is finite (six node types only), it was verified against Blender 5.2.2, and it returns evaluated mesh readback. It omits important behavior an agent needs, notably the create-vs-update semantics, the approved flag, optimistic concurrency via expected_snapshot_id, and failure/rollback behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core payload description, but the wording is inflated with stacked jargon ('Finite transactional full') and the trailing sentence about Blender 5.2.2 verification is more provenance than actionable guidance.

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 9-parameter, 6-required, heavily nested schema with no annotations and no output schema, the description is far from sufficient. It never mentions the mandatory snapshot id on update, the approval gate, or what the mesh readback result looks like, so an agent cannot reliably invoke it from this text alone.

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 9 parameters, so the description must compensate and largely does not. Only 'exact socket identifiers (root semantic names)' adds meaning to the link socket fields; name, modifier_name, group_name, action, parameters, approved and expected_snapshot_id are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it produces a 'full Geometry Nodes specification' with typed nodes/parameters/links and socket identifiers, which conveys the resource, but it never states the action plainly (configure/create/update) and reads as a payload description rather than a verb+resource. It also does not distinguish itself from near-identical siblings like configure_geometry_nodes or configure_curve_geometry.

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 alternatives such as configure_geometry_nodes, nor on prerequisites. The closest thing is the exclusion 'No arbitrary nodes or external references', which is a constraint, not usage routing.

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