Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tris_to_quads

Convert compatible adjacent triangle pairs into quad faces, improving mesh topology for subdivision and deformation.

Instructions

Convert adjacent triangle pairs to quad faces where possible.

Improves topology for subdivision and deformation. Not all triangles can be merged: only adjacent pairs with compatible angles.

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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a key non-obvious behavior: the operation is partially applied ('only adjacent pairs with compatible angles'), so the agent knows not every triangle will be merged. It still omits whether the mesh must be in edit mode, whether the change is in-place/undoable, and whether the active object is implied beyond object_name.

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 a one-line purpose, then benefit, then caveat, then Args. Well structured and mostly tight; the trailing 'Returns: Confirmation dict.' earns little given an output schema already 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 2-parameter mesh operation with an output schema, the description covers purpose, limits, and selection behavior adequately. Remaining gaps are mode/permission prerequisites, which are not stated anywhere else since no annotations are provided.

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: 'selection' is given operational meaning ('ALL' = whole mesh, 'CURRENT' = what is already selected) plus prerequisite guidance for using select_* tools. Only 'object_name' is a bare restatement of the schema title, which is why this is not a 5.

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 ('Convert adjacent triangle pairs to quad faces') and immediately scopes it with 'where possible'. It is trivially distinguishable from the inverse sibling quads_to_tris and from generic retopo tools like remesh or decimate.

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?

Explicitly routes the agent for the selection parameter ('Use the select_* tools to choose first', default 'ALL'), and explains the condition under which work is skipped. It does not, however, name when to prefer this over quads_to_tris or a remesh/decimate workflow.

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