Skip to main content
Glama

set_edge_bevel_weight

Set bevel weight on specific edges to control which edges are bevelled when using a Bevel modifier in weight limit mode. Assign weights from 0 to 1 to selectively bevel edges.

Instructions

Set bevel weight on edges, used with the Bevel modifier (limit_method=WEIGHT).

Only edges with weight > 0 will be bevelled when the modifier uses WEIGHT mode. This lets you selectively bevel specific edges without affecting the whole mesh.

Typical workflow:

  1. set_edge_bevel_weight("Cube", "4,5,6,7", weight=1.0) ← top edges only

  2. add_modifier("Cube", "BEVEL", params='{"width": 0.05, "limit_method": "WEIGHT"}')

Parameters:

  • name: Mesh object name

  • edge_indices: Comma-separated edge indices, or "all"

  • weight: 0.0 (no bevel) to 1.0 (full bevel)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
edge_indicesYes
weightYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains the effect (edges with weight>0 are bevelled) and the typical workflow, but does not mention any destructive consequences or required permissions.

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 well-structured with a clear heading, explanatory paragraph, typical workflow example, and parameter list in a compact format. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and no output schema, the description is complete. It covers the purpose, usage, parameters, and typical workflow adequately for an AI agent to use it correctly.

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

Parameters5/5

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

The schema has 0% description coverage, but the description fully compensates by explaining 'edge_indices' as 'Comma-separated edge indices, or all' and 'weight' as a range 0.0-1.0. It adds significant meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sets bevel weight on edges for use with the Bevel modifier in WEIGHT mode. It distinguishes itself from sibling tools like 'set_edge_crease' by specifying the context.

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?

A typical workflow is provided, showing how to use this tool before adding the modifier. It explains the condition (only edges with weight > 0 are bevelled) but does not explicitly state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/naab007/blender_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server