Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

edit_modifier_stack

Manage Blender modifier stack changes by adding, updating, removing, reordering, toggling visibility, or applying supported modifiers with snapshot validation and approval checks.

Instructions

Finite modifier stack transaction: add/update/remove/reorder/visibility/apply for SUBSURF, BEVEL, SOLIDIFY, BOOLEAN, MIRROR and ARRAY. Requires current inspector snapshot and trusted approval. Apply only the first viewport-enabled modifier; rejects animated, linked and shape-key targets. Finite contract verified in disposable Blender 5.2.2; not universal modifier support.

Input Schema

NameRequiredDescriptionDefault
nameYes
indexNo
actionYes
approvedNo
propertiesNo
show_renderNo
modifier_nameYes
modifier_typeYes
show_viewportNo
expected_snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.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 burden and does disclose useful behavior: approval gating, snapshot preconditions, target restrictions, and single-modifier apply semantics. It still omits what happens on failure, whether remove/apply are reversible, and what the call returns or mutates. The provenance note ('verified in disposable Blender 5.2.2') is a nice trust signal but not behavioral detail.

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?

Four tight sentences, front-loaded with the verb/resource and followed by preconditions, constraints, and scope caveat. Dense jargon ('Finite modifier stack transaction') is offset by concrete enumerations; the Blender 5.2.2 verification clause is borderline but earns its place as a trust boundary.

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

Completeness3/5

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

For a 10-parameter, conditionally-branched mutation tool with no annotations and no output schema, the description covers the safety and scope story reasonably but leaves parameter meaning largely unexplained. An agent would know the preconditions yet still need to guess at index, name vs modifier_name, and per-type property semantics.

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 0% across 10 parameters including a large nested, per-type properties object, so the description must compensate. It names the action and modifier-type enums and hints at expected_snapshot_id, approved, and the visibility toggles, but says nothing about index, name vs modifier_name, or the per-type property fields (levels, width, segments, operation, count, offsets). Partial compensation only.

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 a specific resource (modifier stack) and enumerates both the action set (add/update/remove/reorder/visibility/apply) and the supported modifier types, plus an explicit scope limit ('not universal modifier support'). It does not, however, distinguish itself from plausible siblings such as apply_modifier or configure_modifier, whose names suggest overlapping capability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions ('Requires current inspector snapshot and trusted approval') and explicit exclusions ('rejects animated, linked and shape-key targets'), plus the apply-only-first-viewport-enabled rule. Missing is any statement of when to prefer this tool over the related apply/configure 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