Skip to main content
Glama

Chamfer Edges

chamfer_edges

Bevel selected edges of a Part object by a specified size to create chamfers, with optional per-edge control and partial processing when edges cannot be modified.

Instructions

Chamfer (bevel) edges of a shaped Part object — fillet_edges' counterpart.

edges: e_* tags (preferred), 'EdgeN' strings, or 1-based ints. size: symmetric leg distance mm (> 0). per_edge / allow_partial: as fillet_edges. The base object is hidden. Validated exactly like fillet_edges (#283).

Returns {handle, name, volume (mm^3), edges (indices chamfered), checks {valid, solids, envelope_ok, envelope_growth_mm, envelope_tol_mm}, mode, partial}; when partial, also skipped_edges and a warning. On a failed check the feature is removed and BlendCheckFailed names the offending 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": {
      "handle": "<handle>",
      "edges": "<edges>"
    },
    "name": "chamfer_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoChamfer
sizeNo
edgesYes
handleYes
per_edgeNo
workspaceNoRun this call in this named workspace
allow_partialNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the base object is hidden, features are validated like fillet_edges, and on a failed check the feature is removed with BlendCheckFailed naming offending edges. The destructiveHint=false annotation is not contradicted since the removal is internal cleanup. Only minor gaps (no rate/permission notes) keep it from a 5.

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-loads the core action, then handles parameters, behavior, and return shape in compact telegraphic lines. Dense but every line carries information; no filler.

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?

With no output schema, the description supplies the return shape (handle, name, volume, edges, checks, mode, partial, skipped_edges, warning), which is exactly what an agent needs. Complete enough for correct invocation, though some parameter and failure-mode detail is threaded through references to fillet_edges.

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 coverage is only 14%, so the description must carry the load. It usefully explains edges (e_* tags, EdgeN, 1-based ints) and size (symmetric leg mm > 0), but leaves name, handle, and workspace undocumented. Partial compensation warrants a solid 3.

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?

States a specific verb (Chamfer/bevel) and resource (edges of a shaped Part), and explicitly names itself the counterpart of fillet_edges. An agent can distinguish it from fillet_edges and partdesign_chamfer without opening any schema.

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?

Points to fillet_edges for the semantics of per_edge/allow_partial and validation, giving clear routing context. It stops short of saying exactly when to choose this over partdesign_chamfer or fillet_edges, but the 'counterpart' framing provides adequate orientation.

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