Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Set Construction Geometry

set_construction_geometry
Idempotent

Toggle sketch entities between construction and normal geometry by ID to create reference lines or circles that features ignore. Requires an open sketch and entity IDs from sketch tools.

Instructions

Make sketch entities construction geometry, or normal again, by id.

Use it for reference lines and circles a feature should ignore, such as a line to dimension from or a bolt circle. Needs: an open sketch and ids the sketch tools returned. Changes: each entity's construction setting (setting it to what it already is changes nothing). Returns: construction_geometry with each id's state. An unknown id fails as invalid_input and nothing changes.

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": "set_construction_geometry"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYes`entities` (ids) is required; `construction` is on.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses idempotency semantics in plain terms ('setting it to what it already is changes nothing'), the precondition of an open sketch, and atomic failure behavior ('an unknown id fails as invalid_input and nothing changes'). The annotations only assert idempotentHint/destructiveHint, so this added context is real value.

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 action in the first sentence, then uses explicit Needs/Changes/Returns labels for the rest. No filler; each clause carries a distinct fact (prerequisite, effect, error mode).

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?

An output schema exists, yet the description still summarizes the return shape ('construction_geometry' with each id's state) in one clause. Preconditions, mutation scope, idempotency, and failure mode are all covered for a moderately nested single-parameter tool.

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 schema already documents 'entities' (id provenance, e.g. Line_3) and 'construction' (true/false, default true). The description's 'ids the sketch tools returned' and the 'or normal again' phrasing restate rather than extend that, 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 ('Make ... construction geometry, or normal again') and resource ('sketch entities ... by id'), covering both directions of the toggle. The resource is distinct from every listed sibling, so no disambiguation is needed.

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 a concrete use case ('reference lines and circles a feature should ignore, such as a line to dimension from or a bolt circle') and prerequisites ('an open sketch and ids the sketch tools returned'). It does not name an alternative tool or an explicit when-not condition, which keeps it short of a 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