Skip to main content
Glama

uv_unwrap

Unwraps a mesh object's UV coordinates using angle-based, conformal, or minimum-stretch methods. Mark seams first to get clean, low-distortion results.

Instructions

Unwrap a mesh object's UVs using standard unwrap.

Requires seams to be marked for best results.

Args: object_name: Name of the mesh object. method: Unwrap method - ANGLE_BASED, CONFORMAL, or MINIMUM_STRETCH (the SLIM unwrapper; least distortion, slower).

Returns: Confirmation dict with object name.

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": {
      "object_name": "<object_name>"
    },
    "name": "uv_unwrap"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoANGLE_BASED
object_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / method / enum
      Previous value: -[
      -  "ANGLE_BASED",
      -  "CONFORMAL",
      -  "SLIM"
      -]New value: +[
      +  "ANGLE_BASED",
      +  "CONFORMAL",
      +  "MINIMUM_STRETCH"
      +]
  2. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / method / enum
      Added value: +[
      +  "ANGLE_BASED",
      +  "CONFORMAL",
      +  "SLIM"
      +]
  3. First observedv0.1.0

TDQS

A3.5/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 discloses the seam prerequisite and the mutation intent, and notes a confirmation return. It does not say that existing UV data is overwritten, that the object must own a UV map / be editable, or anything about cost beyond 'slower' for one method — significant omissions for a write operation.

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 purpose sentence, then prerequisite, then a clean Args/Returns block — well structured with no filler. Slightly verbose in the method gloss, but that information is genuinely useful.

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?

An output schema exists, so the brief 'Returns' line is redundant but harmless. The gaps are behavioral rather than structural: overwrite semantics and UV-map prerequisites are missing, which matter for a 2-param mesh mutation tool.

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 does: it names both parameters and explains the method enum, including that MINIMUM_STRETCH is the SLIM unwrapper with least distortion but slower. It stops short of characterizing ANGLE_BASED vs CONFORMAL tradeoffs or object_name resolution rules.

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 states a specific verb and resource — 'Unwrap a mesh object's UVs using standard unwrap' — which clearly distinguishes it from projection-based siblings such as smart_uv_project or set_uv_projection in spirit, though it never names them. Purpose is unambiguous on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Requires seams to be marked for best results" gives a real prerequisite, which is more than most tools offer. But it gives no explicit routing: it never says to use smart_uv_project when seams don't exist or uv_island_operation/pack_uv_islands afterwards, so the agent must infer alternatives from sibling names.

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