Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

fillet_all_edges

Apply fillets to all edges (linear and circular) of a part with adjustable radius, tangent propagation, and minimum edge length filter for uniform edge softening in cast, forged, or plastic parts.

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
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: non-parametric nature, tangent propagation collapsing edges, filtering rules for min_edge_length_mm, and include_arcs effect.

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 for args, returns, and examples, though slightly long; every sentence adds value.

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?

Covers all aspects: purpose, parameters, return format, behavior notes, and examples. Output schema is implicitly provided in description.

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?

Despite 0% schema coverage, the description provides detailed, meaningful explanations for each parameter including typical values, behaviors, and edge cases.

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 'fillet every edge' and provides specific use cases for autoparts, distinguishing it from siblings like 'fillet' and 'break_all_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?

It gives explicit when-to-use contexts (cast/forged parts, brackets, plastic parts) and includes examples, but lacks direct when-not-to-use or alternative tool mentions.

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/solidworks-mcp'

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