Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Sketch Centerline

add_centerline

Draw a construction centerline in an open SolidWorks sketch to serve as a revolve axis or mirror/symmetry reference without adding geometry to the profile.

Instructions

Draw a centreline (construction line) in the open sketch, in mm.

Use it as the axis for create_revolve, or as the line for sketch_mirror and symmetric relations. It is never part of the profile. Needs: an open sketch (create_sketch). Changes: adds a centreline. Returns: centerline with id, start_point and end_point.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe line. Give `x1`, `y1`, `x2`, `y2` (mm; or `start_x`, `start_y`, `end_x`, `end_y`); `construction` is not used.

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 mutation/idempotency hints; the description adds real behavioral context: it is non-profile geometry, requires an open sketch beforehand, and it mutates the sketch by adding an entity. It does not mention duplicate-call behavior or how to remove a centerline, which keeps it at 4.

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, front-loaded sentences plus a compact Needs/Changes/Returns block; nothing is redundant and the action statement comes first.

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?

Output schema exists and the description still names the return shape (`centerline` with `id`, `start_point`, `end_point`), and the sketch prerequisite is covered. Minor gaps remain around repeated invocation and removal, which the annotations do not cover either.

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 each coordinate and alias is already documented in the schema, including the note that `construction` is unused. The description only repeats units (mm) and adds no coordinate-frame or alias-precedence guidance, so baseline 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?

States a specific verb and resource ("Draw a centreline (construction line) in the open sketch") plus units, and immediately clarifies it is construction geometry that "is never part of the profile" — which is exactly what distinguishes it from add_line in the sibling list.

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 downstream uses (axis for `create_revolve`, line for `sketch_mirror` and symmetric relations) and a prerequisite (`create_sketch` / open sketch). It stops short of an explicit "use add_line instead when you want profile geometry" exclusion, so 4 rather than 5.

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