Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Slot

add_slot

Draw straight or arc slots in an open sketch for adjustment slots and keyways, then cut them with create_cut_extrude. Specify width and start/end points to add one closed slot.

Instructions

Draw a slot in the open sketch: straight between two centres, or along an arc.

Use it for adjustment slots and keyways, then cut it (create_cut_extrude). A straight slot takes its two end centres, start and end. An arc slot (kind arc) takes the center of the arc it follows and start and end on that arc, counter-clockwise. Needs: an open sketch (create_sketch). Changes: adds one closed slot. Returns: slot with its id, the points, the width and its area (mm²).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`width` (mm), `start` and `end` (`[x, y]` mm) are required; `kind` is `straight`; `center` for an arc slot.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With annotations only declaring readOnlyHint=false and destructiveHint=false, the description carries real behavioural weight: it states the tool adds exactly one closed slot, selects straight vs arc via `kind`, and specifies the counter-clockwise ordering for an arc slot. It does not discuss undo, sketch state retention or failure modes (e.g. slot exceeding sketch bounds), which keeps it from a 5.

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?

The geometry and usage come first, followed by compact 'Needs / Changes / Returns' labels that make the block scannable. A few clauses restate what the schema already documents (required `width`, `start`, `end`), which is minor redundancy rather than bloat.

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 nested-object addition tool this covers everything an agent needs: geometry for both variants, prerequisites, the mutation it performs, unit conventions and the shape of the result — and an output schema exists so return values need not be spelled out further.

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 the baseline is 3, but the description adds interpretable meaning beyond the field list: it explains that `start`/`end` are end centres for a straight slot versus points on the arc for an arc slot, and that traversal is counter-clockwise. Units (mm) and the returned `area` in mm² are also disambiguated.

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 specific verb and resource — 'Draw a slot in the open sketch' — and immediately enumerates the two geometric variants (straight between two centres, or along an arc). That is enough for an agent to distinguish it from add_line, add_arc, add_rectangle or add_polygon without opening any 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 names concrete use cases ('adjustment slots and keyways'), the required precondition ('Needs: an open sketch (`create_sketch`)') and the natural follow-on operation ('then cut it (`create_cut_extrude`)'). There is no explicit when-not-to-use statement, but no sibling tool overlaps enough to need one.

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