Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

merge_vertices

Combine vertices within a specified distance in a Blender mesh object to remove duplicates. Set threshold and target all or current selection.

Instructions

Merge vertices by distance.

Args: object_name: Name of the mesh object. threshold: Maximum distance between vertices to merge. Range: 0.0-10.0.

selection: "ALL" to act on the whole mesh, or "CURRENT" to act only
    on what is already selected. Use the select_* tools to choose
    first. Defaults to "ALL".

Returns: Confirmation dict with number of removed vertices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectionNoALL
thresholdNo
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / selection
      Added value: +{
+  "default": "ALL",
+  "enum": [
+    "ALL",
+    "CURRENT"
+  ],
+  "title": "Selection",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 does disclose the merge semantics, the threshold range, and the returned confirmation with removed-vertex count, which is useful. However, it never states whether the operation is destructive/irreversible or what happens to the pre-merge topology, which matters for a mesh mutation with zero annotation coverage.

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?

Front-loaded with the purpose, then structured Args/Returns with one line per parameter. No filler, though the Returns note is somewhat redundant given an output schema exists.

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 3-parameter mesh tool with an output schema, the description covers purpose, all parameters, mode selection, and the return shape. It is complete enough to invoke correctly, with the only gap being the destructive/irreversibility caveat.

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 description coverage is 0%, so the description must compensate, and it largely does: it documents object_name, gives threshold meaning plus a 0.0-10.0 range absent from the schema, and explains both enum values for selection. Only the threshold default (0.0001 in schema) is left to 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?

The opening line gives a specific verb+resource ('Merge vertices by distance') with a concrete scoping mechanism (threshold), which reads clearly against mesh-editing siblings like dissolve_verts or join_objects. It stops short of explicitly naming an alternative tool, but the operation is unambiguous.

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?

It explains the two operating modes ('ALL' for the whole mesh vs 'CURRENT' for the current selection) and points the agent at the select_* tools to establish a selection first. That is real when-to-use guidance; only explicit when-not conditions are missing.

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