Skip to main content
Glama

inset_faces

Inset faces on a Blender mesh to create inner geometry for detailing or extrusion. Specify the object name and optional thickness to control the inset depth.

Instructions

Inset faces on a mesh object.

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
nameYes
thicknessNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing: it implies mutation of the mesh but not whether it is destructive, which faces are affected, whether existing geometry is preserved, or whether the object must be selected/active. Only the fact that it operates on a mesh object is conveyed.

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

Conciseness3/5

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

It is a single short sentence with no wasted words, but for a mesh-editing operation it is under-specified rather than genuinely concise, and there is no structure or front-loaded key detail beyond the verb.

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?

An output schema exists so return values need not be described, but the tool is a mutating modeling operation with zero annotation coverage and no parameter documentation, and the description fills none of those gaps. An agent could not reliably call it beyond guessing that 'name' is the mesh.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description must compensate and does not. It never clarifies that 'name' identifies the target mesh object (versus a face or collection) or what 'thickness' means numerically or how it relates to the default of 0.1.

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?

Names a specific modeling operation and its resource: 'Inset faces on a mesh object.' That is enough to distinguish it from neighbors like bevel_mesh or fill_faces, but it never explains what an inset is or what the result looks like, leaving the semantics of the operation implicit.

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 guidance, no statement of prerequisites such as an active mesh, edit-mode, or selected faces, and no reference to any alternative tool. The agent must infer all invocation conditions.

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