Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_uv_seams

Marks, clears, or removes all UV seams on mesh edges, using transactional rollback and snapshot checks to protect Blender edits.

Instructions

Marks, clears, or resets UV seams on mesh edges with transactional rollback and optimistic concurrency checks.

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": "manage_uv_seams"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget mesh object name.
edgesNoList of non-negative integer edge indices to mark or clear. Required for 'mark' and 'clear'.
actionNoOperation: 'mark' (mark specified edges as seams), 'clear' (clear seams from specified edges), or 'clear_all' (remove all seams from mesh). Defaults to 'mark'.mark
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
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?

With no annotations at all, the description carries the full burden. It does disclose two important traits beyond the schema: transactional rollback and optimistic concurrency checking (matching expected_snapshot_id). However, it never flags that 'clear_all' is destructive and irreversible in effect, nor states prerequisites such as required object mode or permissions.

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?

A single compact sentence that front-loads the action set and resource, with the rollback/concurrency qualifier trailing. Nothing is wasted, though the density leaves no room for the caveats an agent would want.

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

Completeness3/5

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

For a six-parameter mutating tool with no annotations and no output schema, the description is only partly sufficient. Rollback and concurrency are covered, but destructive scope, required object state, and any hint of the return payload are absent.

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 including the action enum, edges, and expected_snapshot_id is already documented. The description adds no syntax, format, or edge-index semantics beyond what the schema provides; 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 gives a specific verb set (marks, clears, resets) and a specific resource (UV seams on mesh edges), which is enough to separate it from siblings like inspect_uv_mesh or manage_uv_layers. It stops short of naming an alternative tool or stating the boundary explicitly.

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 / when-not-to-use guidance and no alternatives named. An agent must infer from the enum that 'clear_all' is the bulk-destructive path and that 'edges' is only needed for the per-edge actions, which the schema already states.

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