Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

edit_mesh

Perform atomic, typed mesh edits—create, delete, extrude, bevel, subdivide, and adjust vertices—on the active Blender object with snapshot validation and rollback on error.

Instructions

Atomic typed base-mesh batch on an active-scene Object Mode mesh. Requires a base fingerprint. Component indices reference the initial snapshot, not reindexed intermediate data; deleted references fail. Stages privately, verifies geometry/state and rolls back before commit on error. Supports finite create/delete/extrude/inset/bevel/subdivide/quad-loop-cut/bridge/merge/dissolve/fill/normals/shading/vertex-control actions.

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>",
      "expected_snapshot_id": "<expected_snapshot_id>",
      "operations": "<operations>"
    },
    "name": "edit_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
approvedNoUntrusted; never authorization.
operationsYes
expected_snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses substantial behavior: atomic staging, private staging, geometry/state verification, rollback before commit on error, and that component indices reference the initial snapshot with deleted references failing. It does not cover permissions or rate limits, but for a mutation tool this is strong behavioral context.

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

Conciseness5/5

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

The description is dense but front-loaded, with four sentences that each add distinct information. The long action list is justified by enumerating supported operations, and there is no wasted wording.

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

Completeness4/5

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

For a complex 19-action batch tool with no annotations and no output schema, the description covers the transactional contract, indexing rules, prerequisite fingerprint, and action surface. It omits order-of-operations details and per-action semantics, but those are largely inferable from the action names and schema.

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 25%, so the description must compensate. It adds critical meaning about expected_snapshot_id (the base fingerprint) and component index semantics (initial snapshot, deleted references fail), but it does not explain most parameters such as points, edge_pairs, face_cycles, name, or the operation objects beyond a list of action names.

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 clearly identifies an atomic batch edit tool for base meshes in Object Mode, with a specific verb and scope. It distinguishes itself somewhat by saying 'batch' and listing many supported actions, but it does not explicitly contrast with the many single-operation sibling tools like extrude_mesh or bevel_mesh.

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?

It provides a key prerequisite ('Requires a base fingerprint') and implies usage for multi-operation atomic edits, but never explicitly says when to use this versus single-operation alternatives or when not to use it. Usage is implied rather than guided.

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