Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_uv_layers

Creates, activates, renames, or deletes UV map layers on a mesh object with rollback and concurrency safety.

Instructions

Creates, activates, renames, or deletes UV map layers on a mesh object with rollback and concurrency safety.

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>",
      "layer_name": "<layer_name>"
    },
    "name": "manage_uv_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget mesh object name.
actionNoOperation: 'create' (add new UV layer), 'set_active' (activate layer for editing/rendering), 'rename' (rename existing layer), or 'remove' (delete UV layer). Defaults to 'create'.create
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
new_nameNoNew layer name when action is 'rename'.
layer_nameYesName of the target 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

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It usefully flags 'rollback and concurrency safety', hinting at transactional semantics that align with task_id and expected_snapshot_id, but it never states whether 'remove' is irreversible, what happens to UV data on the removed layer, or what errors arise when a layer name is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause (operations, target, safety traits) carries information an agent needs.

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 a 7-parameter mutation tool with no annotations and no output schema, so the description should do more. It omits return/confirmation behavior, error cases, and the semantics of the deprecated 'approved' flag, leaving meaningful gaps for a destructive-capable operation.

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 parameters are already well documented, and the description's action list merely restates the action enum. It adds no guidance on how new_name pairs with 'rename' or how expected_snapshot_id conflicts are handled, so the baseline 3 applies.

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 names a concrete resource (UV map layers on a mesh object) and four specific verbs (creates, activates, renames, deletes) that map cleanly to the action enum. It is clear what the tool does, though it never contrasts itself with adjacent siblings like manage_uv_seams or pack_uv_islands.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives. An agent learns the possible operations but not the situations that should select this tool over UV unwrap/project/seam tools.

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