Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

apply_modifier

Applies the first viewport-enabled modifier to a target mesh object, making evaluated modifier geometry permanent with snapshot validation and transactional rollback.

Instructions

Apply the first, viewport-enabled modifier in the stack to the target mesh object. Converts evaluated modifier geometry into permanent base mesh geometry with independent readback and transactional rollback.

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>",
      "modifier_name": "<modifier_name>",
      "expected_snapshot_id": "<expected_snapshot_id>"
    },
    "name": "apply_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target mesh object in the active scene.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
object_nameNoAlias for name.
modifier_nameYesName of the modifier to apply (must be the first viewport-enabled modifier in stack).
modifier_typeNoType of modifier to apply. Inferred from object modifier stack if omitted.
target_objectNoAlias for name.
expected_snapshot_idYesModifier stack snapshot fingerprint from inspect_modifier_stack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full load and does disclose that evaluated geometry becomes permanent base mesh data and that the operation has transactional rollback with independent readback. That is meaningful mutation and reversibility context an agent could not infer from the schema, though permission requirements and the fate of remaining modifier stack entries are unstated.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and scope, followed by the two behavioral consequences that matter (permanence and rollback). No filler or redundancy.

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

Completeness4/5

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

For a destructive 8-parameter mutation tool with no annotations and no output schema, the description covers what gets destroyed and that rollback exists. Gaps remain around permissions, error/failure modes, and what happens to the rest of the modifier stack, but the essentials for safe invocation are present.

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 each parameter is already self-documenting, including the deprecated/untrusted approved flag and the snapshot pattern. The description only reinforces the modifier_name ordering constraint; it adds no format or resolution guidance beyond the schema, so baseline 3 applies.

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 verb (Apply) and resource (modifier) plus a precise scope constraint: 'the first, viewport-enabled modifier in the stack'. This clearly separates it from siblings like configure_modifier and edit_modifier_stack, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied through the 'first viewport-enabled modifier' constraint and the mention of the snapshot fingerprint from inspect_modifier_stack, but the description never states when to choose this over configure_modifier or edit_modifier_stack, nor any preconditions beyond the enum-type inference 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