Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Sketch Circle

add_circle

Draws a circle in an open sketch using center coordinates and radius in mm, enabling holes and round bosses; requires an existing sketch.

Instructions

Draw a circle in the open sketch from its centre and radius, in mm.

Use it for holes and round bosses. Needs: an open sketch (create_sketch). Changes: adds a circle (a construction circle with construction). Returns: circle with id, center, radius and diameter. 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_circle"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe circle. `center_x`, `center_y` and `radius` (mm) are required; `construction` is off.

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 declare readOnlyHint=false and destructiveHint=false, so the description builds on that by naming the concrete effect ('adds a circle'), the construction-geometry variant, and the downstream relationship where the returned id feeds add_sketch_constraint and add_sketch_dimension. Idempotency of repeated identical circles on the sketch is left unaddressed, which is a minor gap.

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 core action and its units are front-loaded, followed by use case, prerequisites, effects, and return value in distinct short segments. Every sentence carries information; nothing is padding.

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?

For a mutating sketch primitive it covers the prerequisite sketch state, what is created, and the id contract for follow-on constraint/dimension calls. The return shape is restated even though an output schema exists, which is slightly redundant, and duplicate-call behavior is not stated.

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%, so center_x, center_y, radius and construction are already fully documented in the schema. The description restates centre/radius in mm and clarifies that construction yields construction geometry, but adds no syntax or constraint details beyond that, so the 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?

The description opens with a concrete verb and resource: 'Draw a circle in the open sketch from its centre and radius, in mm.' It also states the domain use ('holes and round bosses'), which makes it distinguishable from add_arc, add_ellipse, and add_rectangle without opening their schemas.

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 gives an explicit prerequisite ('Needs: an open sketch (`create_sketch`)') and a use case ('holes and round bosses'). It stops short of naming when to prefer an alternative sketch primitive, but the context for using it is unambiguous.

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