Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

extrude_faces

Extrudes selected or specified mesh faces in Blender Edit Mode with controllable distance, direction, and region or individual-face handling.

Instructions

Extrude mesh faces in Blender Edit Mode with explicit distance, direction, and selection controls. Supports region extrusion and individual face extrusion. 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": "extrude_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target mesh object in the active scene.
facesNoFaces to extrude: 'selected' (currently selected faces 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.
distanceNoExtrusion distance (positive or negative float). Defaults to 1.0.
directionNo3D direction vector [x, y, z] for extrusion. If omitted, extrudes along face normal(s).
individualNoWhether to extrude faces individually (discrete) or as a connected region. Defaults to False.
expected_snapshot_idNoBase-mesh fingerprint. Required when faces is an explicit index list; mismatches fail before editing.
dissolve_orthogonal_edgesNoWhether to dissolve orthogonal edges during extrusion. Defaults to False.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 add real value by disclosing active-mesh verification, an Edit Mode transition, and topology updates, which signals a mutating operation with preconditions. However, it says nothing about reversibility, undo, whether the scene is saved, or what the call returns, which matters for a 9-parameter mutation tool.

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 short sentences, front-loaded with the verb and resource, and each sentence adds a distinct piece of information (controls, modes, preconditions). No filler or repetition.

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 9-parameter mutating tool with no annotations and no output schema, the description covers mode transition and topology effects but omits return behavior, failure modes beyond snapshot mismatch, and how the operation interacts with selection state. Reasonably complete but with meaningful gaps.

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 description coverage is 100%, so the schema already documents each parameter in detail (including expected_snapshot_id's failure semantics and the deprecated approved flag). The description echoes the key controls (distance, direction, selection) without contradicting them, which is adequate at the baseline.

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?

States a specific verb and resource ("Extrude mesh faces") plus the operating context (Blender Edit Mode) and the controllable dimensions (distance, direction, selection). It does not distinguish itself from the sibling extrude_mesh or explain any difference, 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 Guidelines3/5

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

Usage context is implied by "in Blender Edit Mode" and the region-vs-individual modes, but there is no explicit when-to-use/when-not guidance and no mention of the obvious alternatives (extrude_mesh, inset_faces). An agent must infer selection criteria.

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