Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

sculpt_mesh

Apply snapshot-bound sculpting controls to a Blender mesh: enter or exit sculpt mode, set brushes and settings, draw strokes, voxel remesh, and toggle dynamic topology.

Instructions

Finite snapshot-bound sculpt controls: mode lifecycle, existing sculpt brush/settings, normalized View3D brush stroke, voxel remesh and dynamic topology. Main-thread only; mutations require normal human approval and independent mesh readback.

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": {
      "object_name": "<object_name>",
      "action": "<action>",
      "expected_snapshot_id": "<expected_snapshot_id>"
    },
    "name": "sculpt_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
pointsNo
radiusNo
enabledNo
task_idNo
settingsNo
strengthNo
brush_nameNo
brush_typeNo
iterationsNo
request_idNo
voxel_sizeNo
detail_modeNo
detail_sizeNo
object_nameYes
approval_tokenNo
dynamic_topologyNo
max_displacementNo
preserve_topologyNo
expected_snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses main-thread execution, approval requirements, snapshot binding, and independent readback, but it does not describe the destructive effects of remesh/dyntopo, approval token handling, failure modes, or the state relationship between actions.

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?

The description is compact and front-loads the capability scope before the operational constraints. The single dense opening sentence is efficient, though it packs many concepts without mapping them to the action enum.

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 mutation tool with 20 parameters, nine actions, nested objects, and no output schema or annotations. The description gives a useful high-level overview and safety context, but it is incomplete for correct invocation because it does not explain action-specific parameter requirements or the meaning of key snapshot and approval fields.

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 20 parameters, so the description must compensate and largely does not. It mentions broad categories like brush settings, stroke, and remesh, but gives no meaning for action-specific parameters, the required snapshot ID, approval token, normalized points, radius, or task/request identifiers.

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 ('sculpt controls') and enumerates the main capabilities: mode lifecycle, brush settings, stroke, voxel remesh, and dynamic topology. It is clearly distinguishable from most mesh-editing siblings, though the overlap with sculpt_organic_anatomy is not addressed.

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?

The definition establishes that the tool is main-thread only, snapshot-bound, and requires human approval for mutations, which implies careful usage. However, it does not explicitly say when to use this tool versus inspect_sculpt_state or sculpt_organic_anatomy, nor does it explain which action to choose for a given sculpting goal.

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