Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

uv_project

Projects UV coordinates onto a Blender mesh using Smart UV Project, letting you set angle limits, island margins, and target faces 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": "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.1/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 burden of behavioral disclosure. It never says whether existing UV data is overwritten, whether a missing uv_layer is created, whether the operation is destructive to prior unwraps, or what it returns; for a mesh-mutating operation with 11 parameters including approval and snapshot-id safety fields, that 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 sentences, front-loaded with the core operation and followed by a scope hint; there is no filler or redundancy. It is appropriately sized, though it spends its second sentence on a use-case hint rather than on the missing behavioral detail.

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 mutation tool with 11 parameters, no annotations, and no output schema, the description should at minimum address overwrite behavior and return semantics. It covers purpose and a general use case but leaves the agent without enough to predict the side effects of the call.

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%, with angle_limit, island_margin, and face-selection semantics fully documented in the schema itself, so the baseline is 3. The description's mention of angle limits and island margins merely echoes what the schema already explains in more detail, adding essentially no new meaning beyond it.

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 ("Projects UV coordinates onto a mesh object") and names the underlying algorithm (Blender's Smart UV Project), so the agent knows exactly what operation occurs. However, sibling tools such as smart_uv_project, uv_smart_project, and smart_project appear to cover the same ground, and the description makes no attempt to distinguish this tool from them; the only scoping hint is the "hard-surface or non-organic meshes" clause.

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" gives an implied use case, which is more than nothing. But it never states when to choose this over the similar-sounding sibling unwrap/project tools, nor does it mention prerequisites such as needing an active mesh or edit-mode face selection for the 'selected' faces option.

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