Skip to main content
Glama

bevel_mesh

Bevel mesh edges in Blender to round sharp corners and control edge width and segment count for cleaner models.

Instructions

Bevel mesh edges.

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
nameYes
amountNo
segmentsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 disclosure burden. It does not say whether the operation is destructive, whether it applies a modifier or edits mesh data directly, whether it works only on selected edges, or what happens with invalid input — none of which the single sentence addresses.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is only one sentence, so it is not verbose, but the brevity comes from under-specification rather than efficiency. There is no front-loaded structure because there is essentially no content beyond the tool name.

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?

An output schema exists, so return values need not be explained. However, for a three-parameter mesh-mutation tool with no annotations and zero schema descriptions, the definition omits information an agent needs to call it correctly.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters. The description adds nothing about "name" (object identifier?), "amount" (bevel width, in what units?), or "segments" (edge subdivisions) — these are undocumented in both schema and description.

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

Purpose3/5

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

"Bevel mesh edges" names a specific operation and target, but it is nearly a restatement of the tool name (bevel_mesh) with only the word "edges" added. It gives no hint of how this differs from sibling geometry operations like smooth_mesh, subdivide_mesh, or remesh_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?

There is no guidance on when to bevel versus using another geometry tool, no prerequisites, and no note on when not to use it. The agent must infer usage entirely from the name.

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