Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

smart_uv_project

Projects UV coordinates onto a mesh using Blender's angle-based UV projection, with island margins and face selection for hard-surface or non-organic models.

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": "smart_uv_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.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never says whether an existing UV map is overwritten or a new layer created, whether edit mode or face selection is required, or how the operation interacts with the expected_snapshot_id/approved concurrency fields — for a mesh-mutating tool this is a substantial gap.

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 tight sentences with the algorithm and the fit criteria front-loaded; nothing is padding. It is close to minimal but leaves room that could have been spent on mode/overwrite behavior.

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

Completeness4/5

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

Given the schema fully documents all 11 parameters and there is no output schema to explain, the main remaining obligation is describing how the mutation affects existing UV data — which the description omits. Otherwise the definition covers what an agent needs to select and invoke the tool.

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 structured form, which sets the baseline at 3. The description reinforces that angle limits and island margins govern the projection, but adds no syntax, defaults, or trade-off detail beyond the schema.

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 (projects), resource (UV coordinates onto a mesh object), and names the underlying algorithm (Blender's Smart UV Project). However, with siblings named uv_smart_project, smart_project, and uv_project in the catalog, the description offers no cue distinguishing this tool from those near-identical alternatives.

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 phrase 'ideal for hard-surface or non-organic meshes' implies a use case, which is more than nothing. But it gives no explicit when-not conditions and never routes the agent to uv_unwrap, smart_project, or pack_uv_islands for other cases.

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