Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

pack_uv_islands

Packs UV islands into the unit square with configurable margin and optional rotation, helping prevent overlaps and fit textures within 0–1 UV space.

Instructions

Packs UV islands within the unit square with margin and optional rotation using Blender's island packing engine.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTarget mesh object name.
marginNoMargin spacing between packed UV islands (0.0 to 1.0). Defaults to 0.01.
rotateNoAllow rotation of islands to achieve tighter packing. Defaults to True.
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 active UV layer.
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

C2.9/5.0
Behavior2/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 that islands are packed into the unit square with margin and optional rotation, which is useful behavioral context, but it omits whether existing UVs are overwritten, permission/mode requirements, and treatment of the deprecated 'approved' flag surfaced in the schema.

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?

A single well-formed sentence with the scope front-loaded and no filler. It is efficient, though it could have used one more sentence to carry usage or safety context given the absence of annotations.

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

Completeness2/5

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

For a 7-parameter mutation tool with no annotations and no output schema, the description says nothing about the task_id, expected_snapshot_id, approved, or uv_layer parameters, nor about the expected result. It is under-specified relative to the tool's complexity.

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 is already documented in the schema; the description only echoes margin and rotation, adding no new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 ('Packs') and resource ('UV islands'), plus scope ('within the unit square') and how margin/rotation are applied. This clearly distinguishes a packing operation from sibling UV tools that generate or unwrap UVs, though no sibling is named explicitly.

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 explicit guidance on when to use this tool versus alternatives (e.g., uv_unwrap or smart_uv_project that produce the islands being packed), nor prerequisites such as the mesh needing an existing UV layer. The only contextual hint is the mention of Blender's island packing engine, which implies a post-unwrap step but is not stated as a usage condition.

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