Skip to main content
Glama

pack_uv_islands

Pack UV islands of a mesh object to fit efficiently within UV space, with control over margin, rotation, and scaling to optimize texture layout.

Instructions

Pack UV islands to fit efficiently within the UV space.

Args: object_name: Name of the mesh object. margin: Margin between packed islands (0.0-1.0). rotate: Allow islands to rotate for a tighter fit. rotate_method: ANY, CARDINAL (90 degree steps), AXIS_ALIGNED, AXIS_ALIGNED_X or AXIS_ALIGNED_Y. scale: Scale islands to fill the space. Turn off after set_texel_density, or the pack undoes the density.

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

Input Schema

NameRequiredDescriptionDefault
scaleNo
marginNo
rotateNo
object_nameYes
rotate_methodNoANY

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / rotate
      Added value: +{
      +  "default": true,
      +  "title": "Rotate",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / rotate_method
      Added value: +{
      +  "default": "ANY",
      +  "enum": [
      +    "ANY",
      +    "AXIS_ALIGNED",
      +    "AXIS_ALIGNED_X",
      +    "AXIS_ALIGNED_Y",
      +    "CARDINAL"
      +  ],
      +  "title": "Rotate Method",
      +  "type": "string"
      +}
    • addedInput schema / properties / scale
      Added value: +{
      +  "default": true,
      +  "title": "Scale",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that scaling fills the space and conflicts with texel density, and that rotation produces a tighter fit, plus a brief return shape. It does not say that existing UV coordinates are overwritten, whether a UV map must already exist, or what happens on failure — material gaps for a mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-line purpose followed by a tight Args/Returns block with zero filler. The per-argument lines earn their place because the schema itself carries no descriptions, so this is not duplication.

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 Returns note is a bonus rather than a necessity, and parameter semantics are well covered. What is missing is the operational context an agent needs for a UV-mutating call with no annotations: that current UV layouts are replaced, and any state requirements on the target object.

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 do all the work, and it largely does: every one of the five parameters is explained, including the margin range (0.0-1.0) and the meaning of the rotate_method enum values. The only soft spot is that ANY vs AXIS_ALIGNED is enumerated but not distinguished.

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 ('Pack UV islands ... within the UV space'), which is unambiguous and distinct from siblings like uv_unwrap, smart_uv_project, or uv_island_operation. It never explicitly contrasts itself with those siblings, so an agent must infer that this only re-arranges existing islands rather than creating them.

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?

One genuine usage rule is given: 'Turn off after set_texel_density, or the pack undoes the density' — a real when/when-not hint tied to a named sibling. Beyond that, there is no guidance on when to pack versus unwrap or smart-project, and no stated prerequisites.

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