Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inset_faces

Insets selected, all, or indexed mesh faces in Blender Edit Mode with configurable thickness, depth, boundary, and individual/region controls while verifying the active mesh and updating topology.

Instructions

Inset mesh faces in Blender Edit Mode with configurable thickness, depth, and selection controls. Supports region inset and individual face inset. Enforces active mesh verification, Edit Mode transition, and topology updates.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target mesh object in the active scene.
depthNoInset depth displacement (positive extends outward, negative indents inward). Defaults to 0.0.
facesNoFaces to inset: 'selected' (currently selected in edit mode), 'all' (all faces), or a list of integer face indices [0, 1, 2]. Defaults to 'selected'.selected
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
thicknessNoInset thickness (offset distance inward). Must be non-negative. Defaults to 0.1.
use_outsetNoOutset rather than inset. Defaults to False.
use_boundaryNoWhether to inset open mesh boundary edges. Defaults to True.
use_individualNoWhether to inset each face individually rather than as an entire region. Defaults to False.
expected_snapshot_idNoBase-mesh fingerprint. Required when faces is an explicit index list; mismatches fail before editing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/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, and it does meaningful work: it discloses preconditions (active mesh verification), a mode transition (entering Edit Mode), and side effects (topology updates). What it omits is failure/rollback behavior, undo semantics, and whether the mesh is left selected/modified on partial failure — the snapshot-mismatch guard is only visible in the schema.

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?

Three tight sentences: capability first, then the region/individual distinction, then the operational preconditions. Every sentence contributes information and nothing is padded or repeated.

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 10-parameter mutation tool with no annotations and no output schema, the description covers purpose, modes, and preconditions but says nothing about what the call returns or how failures surface to the caller. An agent can call it correctly, but is under-informed about outcomes.

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 the schema, including the faces enumeration, thickness non-negativity, outset, boundary, and individual flags. The description restates thickness, depth, and selection without adding syntax or constraints beyond it, which is the expected baseline when the schema does the heavy lifting.

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 opens with a concrete verb+resource ('Inset mesh faces in Blender Edit Mode') and names the three controllable axes (thickness, depth, selection). It also distinguishes the two operation modes (region vs. individual). It stops short of differentiating from the sibling 'inset_mesh' or 'extrude_faces', which an agent could plausibly confuse with this tool.

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?

Usage context is implied rather than stated: the tool operates on a mesh already in Edit Mode and enforces 'active mesh verification', which hints at prerequisites. There is no explicit guidance on when to choose this over inset_mesh or extrude_faces, and no stated exclusions or failure conditions an agent should avoid.

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