Skip to main content
Glama
maximedns5

freecad-mcp

by maximedns5

fillet

Round selected edges of a solid in FreeCAD by setting a radius. Rejects sketch bases to prevent invalid geometry errors.

Instructions

Round edges of a solid feature (PartDesign::Fillet).

base_feature MUST be a solid feature (e.g. a Pad or Pocket), never a
sketch — filleting a sketch makes that broken feature the Body's Tip,
and the NEXT pad/pocket then fails with an unrelated "shape is invalid"
error that points nowhere near the real mistake. This tool rejects a
sketch base outright with that explanation instead of letting it happen.

Args:
    doc_name: The name of the document.
    body_name: The name of the PartDesign::Body.
    name: The name to give the new Fillet feature.
    base_feature: The solid feature whose edges to round.
    edges: Edge names on base_feature's shape (e.g. ["Edge3", "Edge7"]).
    radius: Fillet radius in mm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
edgesYes
radiusYes
doc_nameYes
body_nameYes
base_featureYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool rejects a sketch base with an explanation, thereby preventing the otherwise silent 'shape is invalid' failure, and it explains the underlying mechanism of the Tip becoming broken. This goes beyond the basic 'round edges' operation.

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 appropriately sized: the opening sentence states the purpose, the warning paragraph is critical and earns its length, and the Args list is structurally clean and efficient. Every sentence adds value, with no redundant filler or vague phrasing.

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?

The tool has six required parameters and a notably dangerous pitfall (filleting a sketch). The description covers the operation, the base_feature constraint, and the edge/radius parameters thoroughly. Since an output schema exists, return values need not be described, and no critical usage context is missing.

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?

The input schema provides no property descriptions, so the description fully compensates by listing every parameter with context. 'base_feature' is clearly constrained to solid features, 'edges' is given a concrete example format, and all six parameters are explained. This adds meaning well 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 opens with 'Round edges of a solid feature (PartDesign::Fillet)', a specific verb and resource that clearly identifies the operation and object type. It distinguishes this tool from chamfer (rounding vs. beveling) and fillet_edges (solid vs. sketch) by emphasizing the solid-feature requirement.

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 explicitly states the tool is for solid features and strongly warns never to use a sketch, explaining the resulting broken tip and subsequent failures. While it does not name alternative tools such as chamfer or fillet_edges, it provides a clear when-to-use and when-not-to-use condition.

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