Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bevel_edges

Bevel all edges of a Blender mesh by setting width and segments, with options to apply to the whole mesh or only the current selection.

Instructions

Bevel all edges of a mesh.

Args: object_name: Name of the mesh object. width: Bevel width. segments: Number of bevel segments. Range: 1-100.

selection: "ALL" to act on the whole mesh, or "CURRENT" to act only
    on what is already selected. Use the select_* tools to choose
    first. Defaults to "ALL".

Returns: Confirmation dict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
segmentsNo
selectionNoALL
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / selection
      Added value: +{
+  "default": "ALL",
+  "enum": [
+    "ALL",
+    "CURRENT"
+  ],
+  "title": "Selection",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the operation mutates mesh geometry and returns a confirmation dict, but says nothing about destructiveness, reversibility/undo, whether it needs edit mode or a selected/active object, or how it interacts with existing modifiers.

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?

Front-loaded one-sentence statement of purpose, followed by a compact args list and a one-line return note. The per-parameter lines partly restate the schema, but they are short and readable, so nothing is wasteful enough to penalize heavily.

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 4-parameter mesh-editing tool, the description covers purpose, scoping, all parameters, and the return shape, and an output schema exists so return values need no elaboration. The remaining gap is contextual preconditions (edit mode, active object) given the absence of annotations.

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 description coverage is 0%, so the description must compensate and largely does: it explains object_name, width, the 1-100 range on segments, and the meaning plus default of the ALL/CURRENT enum. Only the units/semantics of width (absolute vs relative) remain unstated, a small residual gap.

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 first line gives a specific verb and resource ('Bevel all edges of a mesh'), which distinguishes it from neighboring tools like dissolve_edges, bridge_edge_loops, or inset_faces. Minor friction: 'all edges' sits awkwardly next to a selection parameter that can restrict the operation to a subset, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent how to scope the operation: 'ALL' vs 'CURRENT', and directs it to the select_* sibling tools to make a selection first. It stops short of naming other bevel-like alternatives or stating when a bevel is the wrong choice, so it is clear context without exclusions.

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