Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inset_mesh

Insets faces of a Blender mesh in Edit Mode, letting you set thickness, depth, individual or region mode, and boundary handling before topology updates.

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_mesh"
  }
}

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

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior beyond the name: it verifies the active mesh, transitions the object into Edit Mode, and updates topology. However, it never states that edits mutate the mesh irreversibly, what happens if the mesh is in another mode, or what the response contains.

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?

Three sentences, front-loaded with the action and the environment, with no filler. The final sentence on verification and topology is the least specific but still earns its place as behavioral context.

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 ten-parameter mutation tool with no annotations and no output schema, the description covers purpose and some execution behavior but leaves failure modes, undo semantics, and return values unstated. Adequate, but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all ten parameters and the baseline is 3. The description still adds a little meaning by grouping thickness/depth/selection and mapping to the two inset strategies, but it does not explain use_outset, use_boundary, or the snapshot precondition.

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 specific verb and resource (inset mesh faces) and a specific environment (Blender Edit Mode), and it distinguishes two operating modes (region inset vs. individual face inset). It does not differentiate itself from the sibling tool inset_faces, so it stops short of a 5.

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 explicit guidance on when to choose this tool over alternatives such as inset_faces or extrude_mesh, and no stated preconditions beyond the internal 'active mesh verification' it performs. The agent must infer selection from the name and sibling list.

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