Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

merge_mesh

Merge mesh vertices at center, by collapsed edges, target 3D cursor, or distance threshold, with topological manifold verification to keep topology valid.

Instructions

Merge vertices at center, collapsed edges, target 3D cursor position, or by distance threshold with topological manifold verification.

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": "merge_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoMerge mode: CENTER, COLLAPSE, CURSOR, DISTANCE.CENTER
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.
verticesNoVertices to merge: 'selected', 'all', or an explicit list of non-negative integer indices.selected
object_nameNoAlias for name.
target_objectNoAlias for name.
target_locationNoTarget 3D position [x, y, z] when mode is 'CURSOR'.
distance_thresholdNoDistance threshold when mode is 'DISTANCE'.
expected_snapshot_idNoBase-mesh snapshot fingerprint. Required when vertices is an explicit index list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses topological manifold verification, but does not state that the operation mutates or destroys mesh topology, what permissions or edit-mode state are needed, whether changes are reversible, or what response behavior to expect; the snapshot requirement appears only in the schema.

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?

A single front-loaded sentence with no boilerplate or repetition. It is dense and mostly clear, though phrases like 'collapsed edges' and 'at center' are slightly compressed.

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 mesh mutation with no annotations and no output schema, the description covers the core operation and modes but omits prerequisites, side effects, and return behavior. Full schema coverage mitigates parameter gaps, but the behavioral context remains thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds mode-specific meaning by linking cursor mode to a target 3D position and distance mode to a threshold. It still does not mention name, vertices, aliases, or snapshot semantics, but it meaningfully supplements the schema.

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?

Names a specific operation, merge vertices, and enumerates four supported modes plus topological manifold verification. It is distinguishable from generic mesh editing, though it does not explicitly contrast itself with close siblings such as dissolve_mesh or split_mesh.

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 mode list implies how the tool is used for vertex merging, but there is no explicit when-to-use, when-not-to-use, prerequisite, or sibling-selection guidance. An agent must infer when this is preferable to dissolve or split operations.

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