Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

uv_unwrap

Unwraps selected or all mesh faces into UV coordinates with angle-based or conformal methods, adjustable seam margins, aspect correction, and hole filling.

Instructions

Unwraps selected or all faces of a mesh object into UV coordinates using Blender's Edit Mode unwrap engine. Supports angle-based (ABF) and conformal (LSCM) methods, seam packing margin, aspect correction, and hole filling.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTarget mesh object name.
facesNoFaces to unwrap: 'all' (all faces), 'selected' (currently selected faces in edit mode), or a list of integer face indices [0, 1, 2]. Defaults to 'all'.all
marginNoSpace between UV islands (0.0 to 1.0). Defaults to 0.001.
methodNoUnwrap method: 'ANGLE_BASED' (conformal / ABF, standard) or 'CONFORMAL' (LSCM). Defaults to 'ANGLE_BASED'.ANGLE_BASED
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
uv_layerNoTarget UV map layer name. Defaults to 'UVMap'.UVMap
fill_holesNoVirtually fill holes in mesh before unwrapping to avoid overlapping. Defaults to True.
correct_aspectNoMap UV coordinates taking image or object aspect ratio into account. Defaults to True.
expected_snapshot_idNoOptional SHA-256 snapshot id for optimistic concurrency control.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that unwrapping happens through Blender's Edit Mode engine and that hole filling avoids overlapping islands, but it never says that existing UV layouts in the target layer will be overwritten, whether the object must be active/selected, or that the operation is a mutation.

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?

Two sentences, front-loaded with the core action and followed by a compact capability list. Nothing is padded, though the second sentence duplicates schema content rather than adding routing value.

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?

No annotations and no output schema, but the schema itself is fully described and the description covers the method family, scope of faces, and packing options. The main gaps are the destructive-overwrite behavior and Edit Mode prerequisites, which are meaningful but not fatal for a 10-parameter tool with complete schema coverage.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including `faces`, `margin`, `method`, `fill_holes`, and `correct_aspect` is already documented in structured data, establishing a baseline of 3. The description merely restates those same capabilities (ABF/LSCM, margin, aspect correction, hole filling) without adding format or interaction detail.

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 description uses a specific verb and resource ("Unwraps ... faces of a mesh object into UV coordinates") and names the underlying engine, so the operation is unambiguous. It does not, however, distinguish itself from the sibling `unwrap_mesh`, which by name covers nearly identical ground, leaving the agent to guess which one to pick.

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/when-not-to-use guidance and no mention of alternatives such as `unwrap_mesh`, `smart_uv_project`, or `pack_uv_islands`. The only implicit context is "Edit Mode unwrap engine" and "selected or all faces," which hints at preconditions but never states them as selection rules.

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