Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Select Feature

select_feature
Idempotent

Select a feature, sketch, plane, or component by name in the active SolidWorks document to set up the target for the next operation. Optionally append to the current selection.

Instructions

Select a feature, sketch, plane or component by name in the active document.

Use it to set up a selection that the next SolidWorks operation acts on. append adds to the selection instead of replacing it. A name that can't be selected is an error. Needs: an open document. Changes: the selection only. Returns: data with selected_name and selection_count.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe selection. `feature_name` is required; `append` is off.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Very strong behavioral disclosure. The 'Needs / Changes / Returns' block states the open-document precondition, scopes the side effect to the selection only, and declares that an unselectable name is an error — real context beyond readOnlyHint=false/destructiveHint=false/idempotentHint=true. It is only a notch short of perfect: it doesn't say whether a failed name leaves the prior selection intact or how duplicate names are resolved.

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-loaded with the action, then a labeled Needs/Changes/Returns block. Every sentence carries information; nothing is redundant 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?

Given a single nested parameter, full schema coverage, and an output schema, the description covers purpose, precondition, side-effect scope, error behavior, and return shape. The only shortfall is edge-case behavior around ambiguous or partially matching names.

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 description coverage is 100%, so the baseline is 3. The description restates what the schema already documents for `append` ('adds to the selection instead of replacing it') and adds no new syntax, casing, or disambiguation rules for `feature_name`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus the full set of selectable entity types ('feature, sketch, plane or component ... in the active document'), which implicitly separates it from the face/edge-oriented sibling select_face_edges. It never names an alternative explicitly, so it stops short of a 5.

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?

'Use it to set up a selection that the next SolidWorks operation acts on' gives a clear situational context for calling it. There is no explicit when-not guidance or named alternative for face/edge selection, which a top score would require.

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