Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bevel_edges

Bevels mesh edges or vertices in Blender with configurable offset, segments, profile, and selection; transactional rollback preserves geometry if manifold verification fails.

Instructions

Bevel mesh edges or vertices in Blender with explicit offset, segments, profile, and element selection. Transactional mutation with manifold verification and bit-for-bit rollback.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target mesh object in the active scene.
edgesNoEdges to bevel: 'selected', 'all', or a list of integer edge indices. Defaults to 'all'.all
affectNoWhether to bevel edges or only vertices.EDGES
offsetNoBevel amount/offset distance.
profileNoProfile shape (0.5 is round, < 0.5 concave, > 0.5 convex).
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
segmentsNoNumber of segments in the bevel curve.
verticesNoVertices to bevel when affect is 'VERTICES': 'selected', 'all', or a list of integer vertex indices.
object_nameNoAlias for name.
offset_typeNoMethod of measuring the bevel amount.OFFSET
clamp_overlapNoClamp the bevel amount to prevent overlapping geometry.
target_objectNoAlias for name.
expected_snapshot_idNoBase-mesh snapshot fingerprint. Required when edges or vertices is an explicit index list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 does provide important behavioral context: it is a transactional mutation with manifold verification and bit-for-bit rollback. That discloses mutation risk and failure behavior well, though it omits approval or permission semantics that the schema only partially hints at.

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 two tight sentences, front-loads the action and key parameters, then adds the transactional behavior. There is no redundant or filler wording.

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 14-parameter mutation tool, the description covers purpose and transactional safety but does not explain return behavior, and there is no output schema to fill that gap. It also lacks sibling differentiation against bevel_mesh, leaving some contextual work undone.

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 input schema already documents parameters such as offset, segments, profile, affect, and expected_snapshot_id in detail. The description repeats a subset of those parameter names but adds little meaning beyond the schema, making the baseline 3 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 states a specific verb and resource: bevel mesh edges or vertices in Blender, with explicit offset, segments, profile, and element selection. It is clear what the tool does, but it does not distinguish the tool from the sibling bevel_mesh, so an agent cannot tell from the description alone which one to choose.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative such as bevel_mesh is mentioned. The description implies a precision/transactional bevel workflow but leaves selection between this tool and its sibling 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