Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Sketch Fillet

add_sketch_fillet

Rounds specified corners of an open SolidWorks sketch to a set radius by using each corner's [x, y] point, converting corners to arcs and trimming adjacent entities for 2D profile outlines.

Instructions

Round corners of the open sketch to a radius, picking each corner by its point.

Use it for rounded corners of a 2D profile, such as a cut's outline; round a solid's edges with add_fillet instead, last in the feature tree. Give each corner's [x, y] in sketch mm, where two entities meet (for a rectangle, its corners). Needs: an open sketch (create_sketch) with entities meeting at each corner. Changes: each corner becomes an arc and the entities either side are trimmed back to it. Returns: fillet with one id per corner, the corners and the radius. A corner with no sketch point fails as invalid_input and nothing changes.

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_sketch_fillet"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYes`corners` (a list of `[x, y]` mm) and `radius` (mm).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations: the 'Changes' sentence discloses the geometry mutation (corner becomes an arc, adjacent entities are trimmed back), and the failure clause states atomicity ('fails as `invalid_input` and nothing changes'), which is exactly the transactional context an agent needs before a mutation. The return payload shape is also described. Minor tension: geometry is trimmed back while destructiveHint=false, but that trim is the intended, documented effect of the operation rather than incidental data loss, so it is not a contradiction.

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?

Front-loaded with the action, then structured into labeled 'Needs', 'Changes', and 'Returns' segments. Every clause carries distinct information; there is no restatement of the title or padding.

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 mutating, nested-parameter geometry tool, the definition covers prerequisites, the geometry effect, the failure condition with rollback guarantee, and the return shape. With an output schema present the return summary is a bonus rather than a necessity, and no gap remains that would cause an incorrect call.

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 coverage is 100%, so baseline is 3, but the description adds interpretive meaning beyond the schema: it defines a corner as the point 'where two entities meet' and gives the concrete rectangle mental model, which resolves the real ambiguity of how to pick coordinates. It does not add anything about radius behavior or limits beyond `exclusiveMinimum: 0`, which the schema already carries.

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 precise verb and resource: 'Round corners of the open sketch to a radius, picking each corner by its point.' It immediately distinguishes itself from the nearest sibling by naming `add_fillet` as the tool for solid edges, so an agent can route between the 2D and 3D fillet operations without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('rounded corners of a 2D profile, such as a cut's outline'), an explicit alternative with the condition that selects it (`add_fillet` for solid edges, last in the feature tree), and a stated prerequisite ('an open sketch (`create_sketch`) with entities meeting at each corner'). Nothing about selection is left to inference.

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