Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

dissolve_mesh

Dissolve vertices, edges, or faces from a Blender mesh with manifold verification and boundary preservation to simplify geometry safely.

Instructions

Dissolve vertices, edges, or faces from a mesh object with transactional manifold verification and boundary preservation.

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>"
    },
    "name": "dissolve_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target mesh object in the active scene.
indicesNoIndices to dissolve: 'selected' or an explicit list of non-negative integer indices.selected
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
use_vertsNoDissolve vertices attached to dissolved edges or faces when they become isolated.
object_nameNoAlias for name.
dissolve_typeNoElement domain to dissolve: VERTICES, EDGES, or FACES.EDGES
target_objectNoAlias for name.
use_face_splitNoSplit off surrounding faces when dissolving edges or vertices.
expected_snapshot_idNoBase-mesh snapshot fingerprint. Required when indices is an explicit list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add genuinely useful behavioral traits beyond structured fields: transactional manifold verification and boundary preservation imply a validated, rollback-capable operation. However, it omits destructiveness, reversibility/undo semantics, and the snapshot-precondition workflow that the schema hints at via expected_snapshot_id.

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?

A single front-loaded sentence that states the action, the target domains, and the two most important behavioral guarantees with no filler or redundancy.

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 ten-parameter tool with no annotations and no output schema, the description is thinner than ideal: it says nothing about failure behavior, result reporting, or the surrounding transaction lifecycle despite sibling tools like begin_environment_transaction and commit_environment_transaction. The rich schema compensates for much of the parameter gap, keeping this at the minimum-viable level.

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 all ten parameters are already explained in the input schema, including the enum, the 'selected' default, and the deprecated approved flag. The description adds no parameter-level meaning beyond repeating the three element domains, so the 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?

The description names a specific verb ('Dissolve') and a precise resource set ('vertices, edges, or faces from a mesh object'), matching the dissolve_type enum in the schema. It is clearly distinguishable from sibling operations like merge_mesh or bisect_mesh, though it never explicitly contrasts itself with them.

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 statement of when to use this tool versus alternatives such as merge_mesh, bisect_mesh, or split_mesh, nor any stated exclusions or preconditions. The agent must infer the appropriate context entirely from the verb and 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