Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

uv_smart_project

Projects UV coordinates onto a mesh using Blender's Smart UV Project algorithm, with controls for angle limits, island margins, and face selection.

Instructions

Projects UV coordinates onto a mesh object using Blender's Smart UV Project algorithm. Projects faces based on angle limits and island margins, ideal for hard-surface or non-organic meshes.

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_smart_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget mesh object name.
facesNoFaces to project: 'all' (all faces), 'selected' (currently selected faces in edit mode), or a list of integer face indices [0, 1, 2]. Defaults to 'all'.all
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
angle_limitNoLower angles yield more UV islands with less distortion; higher angles yield fewer islands with more distortion (1.0 to 89.0 degrees). Defaults to 66.0.
area_weightNoWeight projection area by face area (0.0 to 1.0). Defaults to 0.0.
island_marginNoMargin between UV islands (0.0 to 1.0). Defaults to 0.0.
correct_aspectNoMap UVs taking image or object aspect ratio into account. Defaults to True.
scale_to_boundsNoScale UV coordinates to fit the 0.0-1.0 UV bounds. Defaults to False.
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.1/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, and it does not. It never states whether existing UV data on the target layer is overwritten or a new layer is created, whether the object must be in edit mode, or how expected_snapshot_id conflicts are surfaced; the only behavioral detail given (angle/island effects) duplicates the schema's own parameter text.

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 action and algorithm, with no filler. The second sentence is partly redundant with the documented parameters, which keeps it from a perfect score.

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?

This is an 11-parameter destructive-ish UV mutation with no annotations and no output schema, yet the description omits overwrite semantics, mode prerequisites, and return/result information. The gaps are material for an agent deciding whether and how to invoke it safely.

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 of 3 applies. The description's mention of 'angle limits and island margins' merely echoes what the schema already explains in more detail, adding no new semantics for any of the 11 parameters.

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?

Names a specific verb and resource ('Projects UV coordinates onto a mesh object') and identifies the underlying algorithm (Blender's Smart UV Project). However, it gives no basis for distinguishing this from near-identical siblings such as smart_uv_project, smart_project, and uv_project, leaving the agent to guess which to call.

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?

The clause 'ideal for hard-surface or non-organic meshes' implies a usage context, but it is a soft heuristic rather than an explicit when-to-use rule. There is no statement of when NOT to use it, no named alternative (e.g. uv_unwrap, pack_uv_islands) and no prerequisite such as edit-mode selection state.

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