Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

bevel_mesh

Apply bevels to edges or vertices in Blender with explicit offset, segments, profile, and selection; validates manifold geometry and rolls back failed changes.

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

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.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does add real behavioral content beyond the schema: transactional mutation, manifold verification, and bit-for-bit rollback. It still omits failure semantics (what happens when manifold verification fails), permission needs, and any description of the returned result, which matters for a 14-param mutation tool with no output schema.

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?

Two sentences, front-loaded with the operation then the safety posture. No filler or repetition; each clause adds information.

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 complex 14-parameter destructive mesh operation with no annotations and no output schema, the description covers the safety model but not the failure path, the snapshot-id precondition for explicit index lists (schema-only), or the contrast with bevel_edges. It is minimally sufficient rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter in detail; the description only restates field names. Baseline 3 applies, though 'element selection' phrasing mildly signals the edges/vertices/affect interaction.

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 ('Bevel mesh edges or vertices in Blender') and enumerates the controlling knobs (offset, segments, profile, element selection). It does not distinguish itself from the sibling 'bevel_edges', so an agent cannot tell which of the two to pick from this text alone.

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 only implied by the parameter mentions; there is no statement of when to prefer this over bevel_edges, when vertices vs edges affect should be used, or what prerequisites (active scene object, snapshot id) apply. Adequate to orient, insufficient to route.

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