Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

unwrap_mesh

Unwraps selected or all faces of a mesh into UV coordinates using Blender's Edit Mode, with angle-based or conformal methods, margin, 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": "unwrap_mesh"
  }
}

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 must carry the behavioral burden; it does disclose the unwrap methods, hole filling, and aspect correction, which is real value. However, it omits that existing UV data on the target layer is overwritten, that Edit Mode/selection state matters, and what the tool returns, leaving meaningful gaps for a mutation tool.

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 dense sentences, front-loaded with the core action and followed by capability summary; no filler. Slightly list-like in the second sentence but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with no annotations and no output schema, the description covers the main behavioral knobs but leaves out the edit-mode/selection precondition, the overwrite semantics of the UV layer, and any return information. Adequate but with clear gaps.

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 the baseline is 3. The description restates the method options (ABF/LSCM) and mentions margin, aspect, and hole filling, but adds no syntax or format detail beyond what the schema already documents.

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?

States a specific verb and resource ('Unwraps ... faces of a mesh object into UV coordinates') and names the underlying engine (Blender Edit Mode unwrap). It does not differentiate from the sibling uv_unwrap, so an agent cannot tell from the text alone which of the two 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?

No explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as being in Edit Mode or having a selection. The 'selected or all faces' phrasing hints at a usage mode but does not route the agent between this tool and uv_unwrap or inspect_uv_mesh.

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