Skip to main content
Glama
maximedns5

freecad-mcp

by maximedns5

fillet_edges

Round sharp edges on any solid—including boolean results—to create realistic machined parts. Optionally fillet only short edges using a max length filter.

Instructions

Round the edges of ANY solid — the cheapest large gain in realism.

Real machined parts have a radius on essentially every edge. Geometry
built from primitives and booleans reads as obviously synthetic
precisely because everything meets at a sharp corner, so filleting is
usually the single highest-impact finishing step on a part.

Unlike the `fillet` tool (which works on a PartDesign feature inside a
Body), this works on any solid, including boolean results.

Omit `edges` to fillet every edge. Use `max_edge_length` to round only
small detail edges (bosses, ribs, pocket corners) while leaving long
structural edges sharp — usually what you want on a large part.

A radius bigger than the local geometry allows makes the operation fail
rather than silently filleting a subset; reduce the radius or select
fewer edges.

IMPORTANT — fillet parts BEFORE fusing them, not after. Filleting every
edge of a large fused assembly usually fails: the fusion creates many
short, awkward edges where components meet, and one unfilletable edge
rejects the whole operation. Rounding each component while it is still
a simple solid succeeds far more often and gives the same result. If a
fillet on a fused body is refused, that is the first thing to change.

Args:
    doc_name: The document.
    name: Name for the resulting filleted object.
    base: Name of the solid whose edges to round.
    radius: Fillet radius in mm.
    edges: Optional 1-based edge indices. Omit to fillet all edges.
    max_edge_length: Optional filter — only fillet edges no longer than this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYes
nameYes
edgesNo
radiusYes
doc_nameYes
max_edge_lengthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations exist, so the description carries full burden. It discloses failure behavior ('A radius bigger than the local geometry allows makes the operation fail rather than silently filleting a subset') and the why behind fusion failures, going far beyond basic function. This is transparent and builds trust.

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?

The description is lengthy but well-structured, front-loading the purpose and using paragraphs for context, differentiation, and warnings. The 'real machined parts' rationale is useful but could be trimmed; still, 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?

For a parameter-rich tool with no annotations and empty schema, the description covers all parameters, failure modes, and practical sequencing advice (fillet before fusion). The output schema exists, so return-value documentation is not needed. It is complete for an AI agent to select and invoke correctly.

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 coverage is 0%, so the description's Args section is the sole parameter explanation. It defines each parameter clearly, including units (mm), 1-based edge indexing, optionality, and the semantics of `max_edge_length`. This fully compensates for the empty 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 opens with 'Round the edges of ANY solid'—a specific verb and resource—and immediately clarifies its scope (any solid, not just PartDesign features) which distinguishes it from the sibling `fillet` tool. It clearly states what the tool achieves.

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 contrasts with the `fillet` tool ('Unlike the `fillet` tool... this works on any solid'), provides conditional guidance for `max_edge_length`, and gives a critical 'IMPORTANT' warning about filleting before fusing. This is textbook usage direction.

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/maximedns5/freecad-mcp'

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