Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Chamfer

add_chamfer

Bevels edges of the active SolidWorks part by a set distance and angle, or chamfers every edge of a selected face using edge names, coordinates, or current selection.

Instructions

Bevel edges of the active part with a chamfer: distance along one face at angle (45 by default).

Name the edges as "Edge<1>", a point "x,y,z" (metres) or "face:x,y,z" for every edge of a face; or leave edge_names empty to use the current selection (e.g. from select_face_edges). At 45 degrees both legs equal distance; at another angle, flip swaps which face distance is measured on. Needs: an open part with a solid body. Changes: adds a Chamfer feature. Returns: chamfer with name, distance, angle, flip and edges.

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": {
      "input_data": "<input_data>"
    },
    "name": "add_chamfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe chamfer. `distance` (mm) is required; `edge_names` defaults to the current selection.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a non-idempotent write that is not destructive, and the description adds real context beyond that: the 'Needs: an open part with a solid body' precondition, the 'Changes: adds a Chamfer feature' effect, and the returned 'chamfer' payload. It stops short of saying whether the operation is reversible or what a partial/failed edge match leaves behind, but the safety profile is well covered.

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?

Front-loads the core action, then uses labelled 'Needs:'/'Changes:'/'Returns:' blocks that scan quickly. Some of the edge-naming detail and the return-field list duplicate the schema, but nothing is filler and the structure is deliberate.

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?

For a one-parameter wrapper tool with a nested object, the description covers preconditions, mutation effect, selection fallback behaviour and return shape. With an output schema present the return enumeration is optional rather than required, so nothing an agent needs to invoke this correctly is absent.

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 100%, and every nested parameter (flip, angle, distance, edge_names) is already documented in the schema in equivalent words. The description reinforces the key interplay -- 'at 45 degrees both legs equal distance; at another angle, flip swaps which face distance is measured on' -- but adds little syntax or constraint detail the schema does not already carry, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ('Bevel edges of the active part with a chamfer') and immediately scopes the two shaping parameters, so an agent can separate it from add_fillet or the sketch-entity tools at a glance. The verb+resource pairing is concrete rather than a restatement of the name.

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?

Gives explicit edge-addressing options (topology name, 'x,y,z' metre hint, 'face:x,y,z') and states the empty-list case falls back to the live UI selection, with the reasoning that this is most reliable when a user hand-picked edges. What is missing is a direct statement of when to choose this over add_fillet, since both consume edges.

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