Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

fillet_edges

Round selected edges on a FreeCAD feature or shape with a chosen radius to modify geometry safely and undoably.

Instructions

Round selected edges (e.g. ['Edge1', 'Edge2']) on a feature or shape (undoable).

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": {
      "object_name": "<object_name>",
      "edges": "<edges>"
    },
    "name": "fillet_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
edgesYes
radiusNo
doc_nameNo
object_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is largely covered. The description adds the useful fact that the operation is undoable, but says nothing about what happens to the underlying object, whether the radius default of 1 is in document units, or what the response contains.

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?

A single front-loaded sentence with no wasted words; the parenthetical example is compact and useful. It is arguably too terse for a 5-parameter mutation tool, but nothing is redundant.

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

Completeness2/5

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

For a 5-parameter mutation tool with zero schema description coverage, the description covers only the edges argument. Radius semantics (units, default behavior), object_name targeting, and doc_name scoping are all unaddressed, leaving real gaps even though an output schema exists.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate and largely does not. It clarifies the edges parameter with an example format (['Edge1','Edge2']), but radius, object_name, doc_name, and name are left entirely to bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (round/fillet) and resource (selected edges on a feature or shape), which is enough to distinguish it from most siblings. It does not explicitly contrast with chamfer_edges, the nearest alternative, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'on a feature or shape' implies the context of use, and '(undoable)' hints at reversibility, but there is no explicit when-to-use guidance, no mention of when to prefer chamfer_edges, and no stated prerequisites such as an active document or selection.

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