Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Sketch Arc

add_arc

Draw circular arcs in an open sketch using center, three-point, or tangent modes to create rounded ends and curved profile edges.

Instructions

Draw a circular arc in the open sketch: from its centre, through three points, or tangent.

Use it for rounded ends and curved edges of a profile. kind center (the default) takes the centre, start and end, counter-clockwise; three_point takes start, end and a point the arc passes through (through_x, through_y); tangent starts at the end of an existing entity (start) and leaves tangent to it. Needs: an open sketch (create_sketch). Changes: adds an arc. Returns: arc with id, kind, center, start_point and end_point. Its id is what add_sketch_constraint and add_sketch_dimension take.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe arc. `start_x`, `start_y`, `end_x` and `end_y` (mm) are required; `center_x`, `center_y` for `center`; `through_x`, `through_y` for `three_point`.

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 only declare this is a non-idempotent, non-destructive write; the description adds that it appends an arc to the open sketch, requires the sketch to already exist, and specifies the returned entity fields. It does not cover failure behavior when the sketch is closed or the tangent entity is missing, so it is not exhaustive.

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-loaded with the action sentence, then structured with explicit Needs/Changes/Returns labels that make it scannable. There is some duplication of the schema's field descriptions, but nothing is wasted enough to hurt.

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 mutation tool with a nested parameter object and an output schema, the definition covers prerequisites, per-mode parameter expectations, the mutation effect, and the returned `arc` identifier plus its downstream use in add_sketch_constraint/add_sketch_dimension. Nothing an agent needs before calling is missing.

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% and the nested schema already documents every field and the enum meanings, so the schema carries most of the load. The description adds only marginal details such as counter-clockwise ordering and that `tangent` starts from the end of an existing entity, which justifies the baseline 3 rather than more.

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?

"Draw a circular arc in the open sketch" gives a specific verb and resource, then enumerates the three construction modes (center, three_point, tangent), which is enough to separate it from siblings like add_circle or add_line 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 Guidelines4/5

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

It states a concrete use case ("rounded ends and curved edges of a profile") and explains which `kind` to pick for each scenario, plus the prerequisite of an open sketch. It stops short of naming when not to use it or pointing at an alternative tool for the same geometry.

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