Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

fillet_edges

Applies a constant-radius fillet to selected edges or all edges of selected faces, rejecting radii that are too large for the geometry.

Instructions

Add a constant-radius fillet to the selected edges (or to all edges of the selected faces). Select first with select_edges / select_faces. A radius too large for the edges is refused.

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

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
radiusYesRadius of the fillet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description must carry the behavioral burden. It usefully discloses one failure mode ('a radius too large for the edges is refused') and the required prior selection state, but says nothing about whether the operation is destructive to the model tree, whether it can be applied repeatedly to the same edge, or what is returned on success.

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?

Three short sentences with zero filler; the operation and its scope are front-loaded, followed by the prerequisite and the failure condition in descending order of importance.

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 two-parameter geometry mutation with no output schema, the description covers operation, scope, prerequisite selection, and the key failure mode. The only notable omission is any indication of what the operator produces (a feature in the tree) or interaction with existing fillets, which keeps it from being fully complete.

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 coverage is 100%, so both radius and unit are already documented in the schema, which sets the baseline at 3. The description adds only the constraint that an out-of-range radius is rejected, with no unit-inheritance rule or magnitude guidance beyond the 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?

States a specific verb plus resource ('add a constant-radius fillet'), and clarifies the two supported scopes: selected edges or all edges of selected faces. An agent can distinguish this from chamfer_edges or the select_* tools without opening any schema.

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?

Explicitly states the prerequisite workflow: 'Select first with select_edges / select_faces.' That is a real when-to-use condition rather than implied guidance. It does not name an alternative operation (e.g. chamfer_edges) or say when a fillet is inappropriate, so it stops short of full routing guidance.

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