Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bisect_mesh

Split Blender mesh geometry by plane cut, edge subdivision, or edge disconnection, using explicit plane coordinates and bounds to control the cut.

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": "bisect_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. It hints at 'transactional verification' and 'explicit bounds', which gestures at the snapshot/approval machinery, but it never discloses that clear_inner/clear_outer delete geometry, whether the operation is reversible, what happens on verification failure, or what authorization is required for a destructive mesh edit.

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?

A single front-loaded sentence, with the verb-resource purpose first and the mode enumeration and notable parameters after. No filler sentences, though the trailing 'with explicit bounds, plane coordinates, and transactional verification' is somewhat compressed to the point of vagueness.

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 14-parameter destructive geometry operation with no annotations and no output schema, which raises the disclosure bar considerably. The one-sentence description does not address the destructive clear_inner/clear_outer flags, the required snapshot fingerprint for explicit edge lists, or the deprecated/untrusted 'approved' flag, leaving key behavioral context to the 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 100%, so the schema already explains cuts, threshold, clear_inner/clear_outer, method, and expected_snapshot_id. The description echoes plane coordinates and bounds without adding format or constraint detail beyond the schema. Baseline 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 names a specific verb (split) and resource (mesh geometry) and enumerates the three concrete modes: bisect plane cutting, edge subdivision, and edge splitting. This maps cleanly to the BISECT/SUBDIVIDE/SPLIT_EDGES enum, so an agent knows what the tool does. It stops short of distinguishing itself from nearby siblings such as split_mesh, knife_mesh, or dissolve_mesh.

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 lists the available methods but never states when to pick one over another, nor when to prefer a sibling like split_mesh or knife_mesh. There are no prerequisites or exclusions (e.g. that expected_snapshot_id is needed for explicit edge lists). An agent must infer routing from the method enum alone.

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