Skip to main content
Glama

PartDesign Fillet

partdesign_fillet

Fillet selected edges of a PartDesign feature in a FreeCAD Body by applying a radius and validating solid count and bounding-box growth before returning the result.

Instructions

PartDesign Fillet on edges of a feature in a Body. edges accepts e_* tags or 'EdgeN' index strings; radius in mm (> 0).

Validated before a handle is issued, like fillet_edges (issue #283): Shape.isValid(), unchanged solid count, and no growth of the tight bounding box. PartDesign needs it as badly as the Part workbench — r=0.6 on a 40x40x1 pad returns an 'Up-to-date' single solid 15% LARGER than the pad.

per_edge: add the edges one at a time, validating after each. allow_partial: accept a partial result instead of aborting. Off by default.

Returns {handle, name, volume (mm^3), edges (the 'EdgeN' names actually filleted), checks {valid, solids, envelope_ok, envelope_growth_mm, envelope_tol_mm}, mode ('batch' | 'per_edge'), partial}; when partial is True, also skipped_edges and a warnings entry. On a failed check the feature is removed, the Body's Tip is restored, and BlendCheckFailed is raised naming the offending edges and the subset that does fillet cleanly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feature": "<feature>",
      "edges": "<edges>"
    },
    "name": "partdesign_fillet"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPdFillet
edgesYes
radiusNo
featureYes
per_edgeNo
workspaceNoRun this call in this named workspace
allow_partialNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description goes well beyond the annotations by documenting validation checks (`Shape.isValid()`, solid count, bounding-box growth), a concrete failure mode, per-edge validation behavior, partial-result acceptance, and the exact failure recovery behavior including `BlendCheckFailed`. This is rich behavioral context for a mutation tool.

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 front-loaded with purpose and key constraints, then structured around validation, mode flags, return shape, and failure handling. It is somewhat long, but most of the detail is useful for correct invocation; the justification for validation is slightly extraneous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex modification tool with no output schema and sparse parameter descriptions, the description supplies the return shape, failure behavior, validation guarantees, and mode semantics. It still leaves `feature`, `name`, and `workspace` lightly specified, but the core invocation and failure model are covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description must compensate. It gives useful semantics for `edges`, `radius`, `per_edge`, and `allow_partial`, but does not explain the required `feature` parameter, the `name` parameter, or the `workspace` parameter beyond what the schema already provides.

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 states a specific verb and resource: a PartDesign fillet applied to edges of a feature in a Body. It also distinguishes this from the Part workbench fillet by referencing `fillet_edges`, so the agent can tell it apart from sibling fillet/chamfer tools.

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 establishes the correct context (PartDesign Body feature) and names `fillet_edges` as a related operation, but does not explicitly say when to choose this over `fillet_edges` or `partdesign_chamfer`. It does clearly explain when to use the `per_edge` and `allow_partial` modes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools