Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

extrude_mesh

Extrudes selected, all, or indexed mesh faces in Blender Edit Mode with set distance, direction, and region or individual face control.

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

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

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose real traits beyond the schema – active-mesh verification, the Edit Mode transition, and topology updates – but says nothing about side effects on adjacent geometry, undo/irreversibility, or failure modes beyond the pre-edit snapshot check noted 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.

Conciseness4/5

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

Three sentences, front-loaded with the core action and capability summary, with no filler. The third sentence is slightly promotional phrasing ('Enforces...') but still conveys concrete behavior, so trimming is optional rather than needed.

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 mutation tool with no annotations and no output schema, the description covers the action and modes but omits what the tool returns (new geometry, counts, snapshot) and whether results are reversible. The rich schema compensates for parameter gaps, but the behavioral picture is only partly filled in relative to the tool's complexity.

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 one of the 9 parameters is already documented in structured form. The description echoes the main ones (distance, direction, selection, region vs individual) but adds no format, unit, or interaction semantics beyond the schema, so the baseline 3 applies.

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 in Blender Edit Mode') plus the controllable dimensions: distance, direction, selection, and region-vs-individual modes. However, it never distinguishes this tool from the sibling extrude_faces, which by name appears to target the same operation, so an agent has no basis for choosing between them.

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 is implied by the Edit Mode framing and the 'region extrusion and individual face extrusion' capability statement, which suggests the two modes an agent may want. There is no explicit when-to-use/when-not guidance and no mention of the apparent extrude_faces alternative, leaving the routing decision to inference.

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