Skip to main content
Glama

Fillet Edges

fillet_edges

Rounds selected edges of a shaped Part using a given radius and checks the resulting solid for validity, rejecting corrupt geometry before returning a handle.

Instructions

Fillet edges of a shaped Part object. edges: e_* tags (preferred), 'EdgeN' strings, or 1-based ints; radius mm (> 0).

Validated before a handle is issued (#283) — this OCC fillet can silently return corrupt geometry (a 20 mm cube, all 12 edges at r=11, comes back one LARGER solid). Checks: Shape.isValid(), unchanged solid count, no growth of the tight bounding box.

per_edge: add edges one at a time, validating each (slower; for blend-hostile geometry). allow_partial: accept a partial result instead of aborting (off by default).

Returns {handle, name, volume (mm^3), edges (indices filleted), checks {valid, solids, envelope_ok, envelope_growth_mm, envelope_tol_mm}, mode ('batch' | 'per_edge'), partial}; when partial, also skipped_edges and a warning that the solid is NOT the part asked for. On failure it retries per edge, removes the feature and raises BlendCheckFailed naming the offending edges and the subset that fillets cleanly — never a handle to corrupt geometry.

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

Input Schema

NameRequiredDescriptionDefault
edgesYes
handleYes
radiusNo
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.2/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it explains validation before handle issuance, silent corruption risks in OCC fillets, the specific checks performed, retry and rollback behavior on failure, and the guarantee that a corrupt geometry handle is never returned. This is exactly the kind of operational transparency an agent needs 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-structured and front-loaded: purpose first, then key parameters, validation behavior, option semantics, and return/failure shape. Every sentence contributes useful information for a complex modeling operation.

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?

Given the absence of an output schema and low schema description coverage, the description compensates well by documenting the return structure, partial-result behavior, and failure mode. Combined with the annotations, it gives an agent enough to call the tool correctly and understand the risks.

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

Parameters4/5

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

Schema description coverage is low at 17%, so the description must carry most parameter meaning. It explains the important edge formats, radius units and constraint, and the purpose of per_edge and allow_partial, though it does not describe the required handle parameter or workspace behavior.

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?

The description states a specific verb and resource: filleting edges of a shaped Part object. It is clear what operation is performed, though it does not explicitly distinguish this tool from sibling alternatives such as chamfer_edges or partdesign_fillet.

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 description gives useful context for options like per_edge and allow_partial, including when per_edge is appropriate for blend-hostile geometry. However, it does not say when to choose this tool over siblings such as chamfer_edges or partdesign_fillet, nor does it state when not to use it.

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