Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

knife_mesh

Splits a target mesh by plane bisect cuts, edge subdivision, or edge disconnection, using explicit plane coordinates and bounds for controlled geometry edits.

Instructions

Split mesh geometry via bisect plane cutting, edge subdivision, or edge splitting with explicit bounds, plane coordinates, and transactional verification.

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": "knife_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutsNoNumber of cuts for SUBDIVIDE method.
nameYesName of the target mesh object in the active scene.
edgesNoEdges to subdivide or split: 'selected', 'all', or a list of integer edge indices.
methodNoSplit method: BISECT (plane cut), SUBDIVIDE (edge subdivide), or SPLIT_EDGES (disconnect edges).BISECT
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
plane_coNoPoint on plane for bisect [x, y, z]. Defaults to [0.0, 0.0, 0.0].
plane_noNoPlane normal vector for bisect [x, y, z]. Defaults to [0.0, 0.0, 1.0].
thresholdNoDistance threshold for bisect cutting plane.
clear_innerNoFor BISECT: remove geometry behind the plane.
clear_outerNoFor BISECT: remove geometry in front of the plane.
object_nameNoAlias for name.
target_objectNoAlias for name.
expected_snapshot_idNoBase-mesh snapshot fingerprint. Required when edges is an explicit index list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden for a mesh-mutating tool. It mentions 'transactional verification' but does not explain what is verified, what happens to existing geometry, whether the operation is undoable, or how the expected_snapshot_id or deprecated approved flag affect behavior.

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?

The definition is a single front-loaded sentence with no filler, and the core action is stated immediately. It is dense but efficient. The phrase 'transactional verification' is vague enough to slightly reduce precision, but the overall structure is sound.

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?

This is a complex 14-parameter mesh mutation tool with no annotations and no output schema. The description does not cover transactional behavior, failure modes, return values, or operational prerequisites. Given that complexity, one sentence is not complete enough to guide an agent safely.

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 all 14 parameters are already documented in the input schema. The description references explicit bounds, plane coordinates, and methods, but adds no extra syntax, constraints, or usage nuance beyond what the schema already provides. The baseline of 3 is appropriate.

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 gives a specific verb and resource: split mesh geometry. It also names three concrete modes: bisect plane cutting, edge subdivision, and edge splitting. However, it does not distinguish this tool from sibling tools such as bisect_mesh or split_mesh, so an agent cannot infer which one to choose from purpose alone.

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?

The description implies this tool is for splitting mesh geometry, but it gives no explicit when-to-use guidance. It does not say why to choose knife_mesh over bisect_mesh, split_mesh, or dissolve_mesh, nor does it state preconditions such as mesh selection state or edit mode.

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