Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_modeling_object

Applies snapshot-bound local or world transforms, selections, and parent/clear-parent operations to Blender objects with pivot control, rejecting unsupported shear, singular scales, and cycles.

Instructions

Snapshot-bound finite local/world delta transform with explicit pivot, world-preserving parent/clear_parent, selection. Rejects shear, singular scales, animated/constrained/linked targets and cycles. Finite contract verified in disposable Blender 5.2.2; broader domain remains partial.

Input Schema

NameRequiredDescriptionDefault
nameYes
pivotNo
scaleNo
spaceNo
stateNo
actionYes
approvedNo
rotationNo
make_activeNo
parent_nameNo
translationNo
deselect_allNo
expected_snapshot_idYes

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 full behavioral burden and it does disclose real traits: snapshot binding via expected_snapshot_id, world-preserving parenting, and explicit rejection of shear, singular scales, animated/constrained/linked targets and cycles, plus a note that the finite contract was verified only in Blender 5.2.2 with a partial broader domain. That is meaningful context. However, it omits mutation safety, what the approved flag does, and what happens when the snapshot does not match.

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-loaded, and every clause is packed with information. But the density crosses into obscurity ('finite local/world delta transform with explicit pivot'), and the trailing verification caveat consumes space without helping the agent decide how to call the 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?

This is a complex conditional tool: 13 parameters across four action branches, no annotations and no output schema. The description covers rejection criteria and snapshot binding but leaves branch-specific requirements, the approval gate, and return behavior unexplained, so it is not complete enough for confident invocation.

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 13 parameters, so the description must compensate and only partly does. It hints at pivot, local/world space, scale validity and snapshot binding, but says nothing about approved, state, make_active, deselect_all, name, or the translation/rotation semantics. Over half the parameters remain undocumented anywhere.

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 enumerates the four behaviors in play (delta transform with pivot, parent, clear_parent, selection), which maps to the action enum, but the phrasing is dense jargon rather than a plain verb+resource statement. An agent can infer it configures object transform/parenting state, yet would still need to read the schema to know the exact operations. Siblings like transform_object and select_object are not mentioned, so differentiation is absent.

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 when-to-use guidance and no named alternative, despite closely overlapping siblings (transform_object, select_object, align_object_grid). The only conditional content is what inputs are rejected, which is a constraint rather than a usage guideline. The agent is left to infer when this tool is preferred over the simpler siblings.

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