Skip to main content
Glama

chamfer

Bevel one or more edges by setting a distance and angle. Applies standard autoparts chamfers for deburring or bolt-hole lead-ins.

Instructions

Chaflán — bevel one or more edges (distance + angle).

Edge addressing, the selector schema (recommended), failure modes, and the batch-all-identical-edges-in-ONE-call rule are IDENTICAL to fillet — see its description. E.g. chamfer every hole rim at the top face (z≈10): chamfer(selector={"filter": {"geom": "circle", "axis": "z", "at_mm": 10, "tol_mm": 0.5}}, distance_mm=1.0)

Standard autoparts use: bolt-hole entry chamfers (lead-in for assembly), deburred edges on machined parts, parting-line breaks on cast housings. 45° distance-angle is the autoparts default; distance-distance and vertex chamfers are deferred.

Args: edge_midpoints_mm: Optional. Edge addressing by midpoint (line edges; from list_edges() e["midpoint_mm"]). distance_mm: Chamfer leg length (the distance the chamfer extends along the edge's faces). Must be > 0. Typical autoparts values: 0.3-0.5mm for deburr, 1-2mm for bolt-hole lead-ins. angle_deg: Angle from the reference face. Must be in (0, 90). Default 45° (standard for almost all autoparts chamfers). flip: If True, the angle is measured from the OTHER adjacent face. Useful when the default direction goes the wrong way. edge_indices: Optional. Edge addressing by (body, index) — required for closed-loop circular edges (midpoint_mm is None for those).

Returns the resulting Chaflán feature (name, type="chamfer", dims).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flipNo
selectorNo
angle_degNo
distance_mmNo
edge_circlesNo
edge_indicesNo
edge_midpoints_mmNo
Behavior5/5

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

With no annotations, the description carries full burden. It discloses failure modes (via fillet reference), batch-all-identical-edges rule, default values, parameter constraints, and return value. Very transparent.

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?

Well-structured with clear sections and example, but slightly verbose. Could be trimmed without losing meaning.

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?

Covers usage, parameters, return value, and industry context. Lacks details on error handling and edge cases, but overall comprehensive given complexity (7 params, no output schema).

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?

Adds substantial meaning to most parameters (e.g., edge_midpoints_mm from list_edges, distance_mm typical values, angle_deg default). However, 'edge_circles' parameter is not explained, and schema coverage is 0%.

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?

Clearly states 'bevel one or more edges (distance + angle)' with specific verb and resource. Distinguishes from sibling 'fillet' via explicit reference.

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

Usage Guidelines5/5

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

Provides extensive guidelines: references fillet for identical rules, offers example, lists standard autoparts use cases, and mentions deferred types. Explicitly tells when to use and alternative tools.

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/danielproxd2/MCP_CAD'

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