Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Cosmetic Thread

add_cosmetic_thread

Add a drawing-visible cosmetic thread to a hole or shaft by selecting the circular edge and thread size; the model volume stays unchanged.

Instructions

Add a cosmetic thread to a hole or shaft, so drawings show the thread callout.

Pick the circular edge where the thread starts with a point on it (mm). The thread is drawn, not modelled, so the volume must not change; it fails if it does. Needs: an open part with a round edge at edge_point. Changes: adds a Cosmetic Thread feature. Returns: thread with name, size, diameter_mm, end_type and depth_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_cosmetic_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe thread. `edge_point` and `size` are required; `diameter` comes from a metric size; blind (the default) needs `depth`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations (readOnly/non-idempotent/non-destructive) by disclosing the key behavioral trait that this is drawn, not modelled, and that the operation fails if volume changes. It also states what is created and what is returned. Missing only details such as whether re-running on the same edge duplicates the feature, which matters given idempotentHint=false.

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-loads the purpose in one sentence, then uses compact "Needs: / Changes: / Returns:" labels so each remaining sentence carries distinct information. No padding or redundancy.

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 single-parameter, deeply nested mutation with an output schema present, the description covers prerequisites, failure mode, side effect, and a summary of the return fields. Nothing needed to call it correctly is absent.

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 already 100%, so the baseline is 3; the description still adds cross-field meaning, noting that `size` and `edge_point` are required, that `diameter` is derived from a metric size, and that blind end type needs `depth`. It reinforces rather than merely repeats the schema.

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 ("Add a cosmetic thread to a hole or shaft") plus the downstream intent ("so drawings show the thread callout"), which separates it from the solid-geometry siblings like add_fillet or add_chamfer. An agent can tell what it produces without opening the 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?

Gives concrete prerequisites ("an open part with a round edge at `edge_point`") and a hard failure condition ("it fails if [the volume changes]"), plus how to pick the edge location. It does not name an alternative tool for modelling a real thread, but the when-to-use context is otherwise explicit.

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