Skip to main content
Glama

break_all_edges

Deburr every linear and circular edge on a part or selected body with a single chamfer operation, eliminating the need for manual edge selection and multiple steps.

Instructions

Desbarbar todas las aristas — chamfer every edge (linear and circular by default).

Universal edge-break for autoparts: every machined drawing calls out edge breaks per ISO 13715, every Tier 1 customer requires deburred edges before assembly. This composite implements "achaflana todo" / "desbarbar todo" in one call instead of three (list_edges + filter

  • chamfer).

Args: distance_mm: Chamfer leg length. Default 0.5mm — typical machined-edge deburr. Use 0.3mm for fine deburr or 1.0mm for noticeable lead-ins. angle_deg: Angle from reference face. Default 45° (autoparts standard for ~99% of cases). min_edge_length_mm: Skip linear edges shorter than this. Default 1.0mm — filters tiny sub-edges left over from prior fillet/chamfer features. Circular edges (arc / circle) skip this filter — their length_mm is the chord length and isn't meaningful for the deburr decision. body_name: If given, only chamfer edges of that body. Else enumerate all solid bodies in the active part. include_arcs: If True (default), include arc and circle edges in the chamfer set. Required for round autoparts (rines, cubos, discos de freno, engranes) where every edge is circular. Set False for the legacy linear-only behavior.

Returns: { "feature": {"name": "Chaflán1", "type": "chamfer", "dimensions": {...}}, "edges_chamfered": int, }

Caveat: NOT parametric — re-running with different distance_mm requires deleting the feature first. After break_all_edges runs, the part has many short sub-edges from the chamfer; calling fillet_all_edges next will re-process those unless min_edge_length_mm filters them out. Recommend using only one edge-break tool per part.

Example — standard 0.5mm × 45° deburr on every edge: break_all_edges()

Example — heavy 1mm × 45° on a single body in a multi-body part: break_all_edges(distance_mm=1.0, body_name="Saliente-Extruir2")

Example — strict linear-only deburr (skip circular edges): break_all_edges(include_arcs=False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
angle_degNo
body_nameNo
distance_mmNo
include_arcsNo
min_edge_length_mmNo
Behavior5/5

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

With no annotations, description fully discloses behavior: not parametric, creates sub-edges, modifies the part, returns a feature object with chamfered edges count, and explains default handling of circular edges. No contradictions.

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 context paragraph, bulleted args, return info, caveat, and examples. Front-loaded with purpose. Slightly verbose but every section adds value; minor trim could improve conciseness.

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 lack of annotations and output schema, description covers all necessary aspects: when to use, parameter details, return structure, side effects, interaction with other tools, and practical examples. Complete for correct invocation.

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?

Schema has 0% description coverage, but description provides rich detail for all 5 parameters: defaults, typical values, edge cases (e.g., circular edges skip min_edge_length_mm), and the purpose of include_arcs for round parts. Fully compensates for schema gap.

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 it chamfers every edge (linear and circular) in one call, designed for autoparts edge breaks per ISO 13715. Distinguishes from sibling tools like chamfer (requires selection) and fillet_all_edges by combining list_edges + filter + chamfer.

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?

Explicitly says when to use (universal deburring for autoparts), gives examples (standard deburr, single body, linear-only), warns about non-parametric nature and interaction with fillet_all_edges, and recommends using only one edge-break tool per part.

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