Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inset_faces

Inset mesh faces to create borders or frames around each face for adding detail or preparing extrusion. Select specific faces first; using 'ALL' on closed meshes has no effect.

Instructions

Inset all faces of a mesh, creating a border/frame around each face.

Core hard-surface modeling operation for adding detail, panel lines, or preparing faces for extrusion.

On a closed mesh, selection="ALL" does nothing: a region with no boundary has nothing to inset from, and Blender reports success having changed nothing. Measured on a default cube in 5.1, the vertex, edge and face counts are identical afterwards. Select the faces you mean and pass selection="CURRENT".

Args: object_name: Name of the mesh object. thickness: Inset thickness (border width). Range: 0.0-10.0. depth: Inset depth (positive=outward, negative=inward). Range: -10.0 to 10.0.

selection: "ALL" to act on the whole mesh, or "CURRENT" to act only
    on what is already selected. Use the select_* tools to choose
    first. Defaults to "ALL".

Returns: Confirmation dict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
selectionNoALL
thicknessNo
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / selection
      Added value: +{
+  "default": "ALL",
+  "enum": [
+    "ALL",
+    "CURRENT"
+  ],
+  "title": "Selection",
+  "type": "string"
+}
  2. Addedv1.2.2

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are present, so the description carries the full burden — and it does so exceptionally, disclosing a silent-failure gotcha ("ALL" on a closed mesh succeeds but changes nothing, vertex/edge/face counts identical) rather than a generic mutation disclaimer. That is a non-obvious behavioral trait an agent would otherwise hit blind.

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?

Front-loaded with the core action, then usage context, then the critical caveat, then args and returns — a sensible order with no wasted sections. Slightly verbose in the cube-measurement anecdote, but it is evidence supporting the caveat rather than filler.

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

Completeness5/5

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

For a 4-param mutation tool with no annotations and an output schema, the description covers purpose, when-to-use, prerequisites, all parameter semantics, a failure mode, and return type. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it documents all four parameters: object_name's purpose, thickness as border width with range 0.0-10.0, depth with sign semantics (positive=outward, negative=inward) and range, and selection's enum semantics plus its default. This exceeds the schema, which carries no per-field text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Inset all faces of a mesh") and the resulting geometry (border/frame around each face), which immediately distinguishes it from siblings like extrude_faces and bevel_edges. An agent can pick this tool over its neighbors without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames it as a core hard-surface modeling operation for adding detail, panel lines, or preparing faces for extrusion, and names the prerequisite workflow ("Use the select_* tools to choose first"). It also gives a concrete when-NOT-to-use condition: selection="ALL" on a closed mesh does nothing. This is exactly the routing guidance the dimension asks for.

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