Skip to main content
Glama

merge_vertices

Merge vertices by distance in Blender to weld duplicate points and clean up mesh geometry for modeling and topology fixes.

Instructions

Merge vertices by distance.

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_vertices"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
distanceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state that this mutates the mesh in place, whether the merge is reversible, how the operation is scoped to the named object, or whether vertices on UV seams/attributes are affected.

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 single short sentence is front-loaded and free of filler, which is structurally sound. Its brevity reflects under-specification rather than waste, which is penalized in other dimensions.

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?

An output schema exists, so return values need not be explained, but for a mesh-mutating tool with no annotations and zero parameter documentation the description is far too thin. An agent cannot determine the target object, the units of the distance threshold, or the side effects before invoking it.

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% for 2 parameters, so the description must compensate and largely fails. 'By distance' hints that the threshold parameter exists but gives no units, no meaning of the default 0.0001, and 'name' is never explained at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ('Merge vertices') plus the criterion ('by distance'), so the operation itself is identifiable. However, it never says what is being operated on — the required 'name' parameter is presumably the mesh/object, but the description leaves that to inference, and there is no distinguishing language against other mesh-editing siblings.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or when not to merge (e.g. vs. other cleanup operations). The agent must guess the context entirely from the name.

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