Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dissolve_faces

Merges faces into surrounding geometry to remove them without creating holes, keeping the mesh structure intact.

Instructions

Dissolve all faces, merging them into surrounding geometry.

Removes faces while keeping the surrounding mesh structure intact. Cleaner than deleting faces which leaves holes.

Args: object_name: Name of the mesh object.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectionNoALL
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. Addedv1.2.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral outcome (faces removed but surrounding mesh structure kept intact, unlike deletion which leaves holes) and what is returned ('Confirmation dict.'). It does not say whether the operation is reversible or what preconditions (e.g., manifold geometry, selection mode) apply.

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 sections. The opening two sentences overlap slightly (merge scope vs. holes contrast), but each still earns its place and the whole thing is short.

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 two-parameter mesh operation with an output schema (so return values need no elaboration), the description covers purpose, parameter semantics, usage guidance, and behavioral contrast. Minor gap: no statement about prerequisites or reversibility on a destructive mesh edit.

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

Parameters5/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 does: it explains both params — object_name as the mesh to act on, and selection as 'ALL' vs 'CURRENT' with the default and the prerequisite select_* step. This adds real meaning beyond the bare enum in the schema.

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

Purpose5/5

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

States a specific verb and resource ('Dissolve all faces, merging them into surrounding geometry') and immediately distinguishes the operation from plain deletion ('Cleaner than deleting faces which leaves holes'). An agent can distinguish this from siblings like dissolve_edges, dissolve_verts, or separate_mesh without extra context.

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?

Gives concrete guidance for the selection parameter: use the select_* tools to choose first when passing 'CURRENT', and default is 'ALL'. The contrast with deletion implies when to prefer this tool, but there is no explicit 'when not to use' or named alternative beyond the passing mention of deleting faces.

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