Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Features

list_features
Read-onlyIdempotent

Lists the active part or assembly feature tree in order, helping you find exact feature names before deleting, suppressing, or renaming them.

Instructions

List the feature tree of the active part or assembly, in order.

Use it before editing a model, to find a feature's exact name for delete_feature, suppress_feature or rename_feature. For an assembly it also lists each component's features, down to max_assembly_depth levels. Needs: an open part or assembly. Read-only. Returns: features (each with name, type, suppressed and, in an assembly, component), count, and assembly_tree, the same list grouped by component.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesWhat to list. Nothing is required: `include_suppressed` (off) and `max_assembly_depth` (2) have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description only needs to add context — and it does, stating the prerequisite 'Needs: an open part or assembly' and how assembly traversal behaves. It restates 'Read-only,' which is redundant with annotations, and the return-field breakdown overlaps the output schema.

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?

Front-loaded with the core action, then structured into 'Use it before...', 'Needs:' and 'Returns:' segments that are easy to scan. The Returns sentence duplicates the output schema, so a small amount of text does not earn its place.

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?

Covers purpose, prerequisite state, sibling handoffs and return shape, while annotations supply the safety profile and an output schema exists for return values. Nothing an agent needs in order to invoke this correctly is missing.

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 3 is the baseline, but the description adds real meaning by explaining that assembly listing recurses 'down to max_assembly_depth levels' and that each feature carries a component field in assemblies. It does not explain include_suppressed, leaving that entirely to 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 plus scope: 'List the feature tree of the active part or assembly, in order.' That clearly separates it from sibling listing tools such as list_components or list_configurations, which cover different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule ('before editing a model') and names the three downstream tools that consume the returned names (delete_feature, suppress_feature, rename_feature). An agent knows both when to call it and why, with no alternatives left to infer.

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