Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

smart_project

Projects UV coordinates onto a mesh using Blender's Smart UV Project algorithm with angle limits and island margins, suited 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_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 provided, so the description carries the full behavioral burden. It never states that this is a mutating operation, whether existing UV data in the target uv_layer is overwritten, whether edit mode or a selection is required, or how the deprecated 'approved' flag and 'expected_snapshot_id' concurrency control behave. The only behavioral detail given (angle vs. island count) merely restates schema parameter descriptions.

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 core action front-loaded and the use-case qualifier second. There is mild redundancy in opening both sentences with 'Projects', but no filler or wasted clauses.

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?

With 11 parameters, no annotations, and no output schema, the definition should do more work than two sentences. It omits the mutation semantics, the meaning of the workflow-oriented parameters (task_id, approved, expected_snapshot_id), and any statement about what the returned or resulting state looks like.

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 one of the 11 parameters is already documented at the schema level, which sets the baseline at 3. The description adds only a high-level nod to 'angle limits and island margins' and nothing about faces, uv_layer, task_id, or optimistic concurrency, so it does not exceed 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?

Names a specific verb and resource (projects UV coordinates onto a mesh object) and identifies the underlying algorithm, Smart UV Project. It does not distinguish itself from the closely-named siblings smart_uv_project, uv_smart_project, and uv_project, so an agent cannot tell which to pick from the text alone.

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 usage context, which is more than nothing. However, there are no explicit when-not conditions, no prerequisites such as edit mode or selection state, and no pointer to an alternative sibling tool for organic meshes.

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