Skip to main content
Glama

fillet_all_edges

Apply fillets to all edges of a model, with adjustable radius and tangent propagation. Optionally filter by edge length or body, and include circular edges.

Instructions

Redondear todas las aristas — fillet every edge (linear and circular by default).

Universal edge softening for autoparts: cast/forged parts get transition radii (ISO 8062), structural brackets get stress-relief fillets, plastic injection-molded parts need rounded edges. This composite implements "redondea todo" in one call.

Args: radius_mm: Fillet radius. Default 1.0mm — typical machined-edge softening. Use 2-5mm for cast-part transitions, R = 0.5-1.5 × wall_thickness for plastic ribs. tangent_propagation: If True (default), SW propagates the fillet along tangent-continuous neighboring edges, producing one smooth filleted region for rows of co-linear edges. Pass False for strict per-edge fillets (each edge gets its own region). True is what most "redondea todo" intents mean. min_edge_length_mm: Skip linear edges shorter than this. Default 1.0mm. Circular edges (arc / circle) skip this filter — their length_mm is the chord length and isn't meaningful for the softening decision. body_name: If given, only fillet edges of that body. include_arcs: If True (default), include arc and circle edges in the fillet 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": "Redondeo1", "type": "fillet", "dimensions": {...}}, "edges_filleted": int, }

Caveat: NOT parametric — re-radiusing requires deleting the feature. With tangent_propagation=True, SW collapses adjacent edges into one filleted region; the resulting feature may show fewer "branches" than edges_filleted in the SW UI tree.

Example — soften every edge of a bracket at R=1mm: fillet_all_edges()

Example — large R=5mm transition on cast housing, no tangent prop: fillet_all_edges(radius_mm=5.0, tangent_propagation=False)

Example — strict linear-only fillet (skip circular edges): fillet_all_edges(include_arcs=False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
body_nameNo
radius_mmNo
include_arcsNo
min_edge_length_mmNo
tangent_propagationNo
Behavior4/5

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

Despite no annotations, the description discloses critical behavioral traits: non-parametric nature (re-radiusing requires deleting the feature), tangent propagation collapsing edges, and the return format. It also explains edge filtering behavior for circular edges. These details exceed what annotations typically provide.

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: a brief summary, usage context, detailed parameter explanations with defaults and recommendations, return format, caveats, and examples. Every sentence adds necessary value without redundancy, and the structure is front-loaded with the core purpose.

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 5 parameters, no output schema, and no annotations, the description is highly complete. It covers all parameters, return value explicitly with field names and types, caveats about non-parametric behavior and feature collapse, and three practical examples. It also incorporates domain-specific context (ISO 8062, autoparts).

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?

With 0% schema description coverage, the description fully compensates by explaining every parameter: radius_mm default and recommended ranges for different contexts, tangent_propagation behavior, min_edge_length_mm skip logic, body_name scoping, and include_arcs rationale. This provides actionable meaning beyond the raw 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 the tool's purpose: 'fillet every edge (linear and circular by default)' and frames it as a composite for 'redondea todo' in one call. This specific verb+resource differentiates it from the sibling 'fillet' tool, which likely handles selective edges.

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?

The description provides explicit when-to-use guidance with domain-specific examples like cast/forged parts, structural brackets, and plastic injection-molded parts, including suggested radius ranges. However, it does not directly contrast with the sibling 'fillet' tool or specify when not to use this tool, slightly limiting guidance.

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