Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Classify Feature Tree

classify_feature_tree
Read-onlyIdempotent

Classifies a SolidWorks model's feature tree as part, sheet metal, assembly, or drawing and recommends the workflow to use before rebuilding or editing an unfamiliar model.

Instructions

Classify the active model's kind (part, sheet metal, assembly, drawing and so on) from its feature tree, and suggest how to work on it.

Use it before rebuilding or editing an unfamiliar model, to pick a workflow. It reads the model unless you pass model_info and features you already have (from get_model_info and list_features). Needs: an open document, unless both are passed. Read-only. Returns: classification with family, recommended_workflow, confidence, needs_vba, evidence, warnings, next_actions and feature_count, plus the model_info and features used.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesWhat to classify. Nothing is required: pass `model_info` and `features` to classify them without reading the model; `include_suppressed` is off by default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, and the description's "Read-only" line largely repeats them. What it genuinely adds is that the tool may or may not touch the open document depending on whether inputs are supplied, and which prerequisite (an active document) gates it — behavior not derivable from the annotations.

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 purpose, then labeled sentences for input mode, requirements and returns. The trailing enumeration of eight return fields is partly wasted since an output schema exists, and "Read-only" duplicates the annotation, but nothing else is 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?

For a classification tool with a nested input object and a full output schema, the description covers purpose, prerequisites, the two input modes and what comes back. The only meaningful omission is that suppressed features are included by default when reading the model, which can change the classification result.

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 real meaning by stating where the optional model_info and features payloads come from (get_model_info, list_features) — chaining information absent from the schema. It never mentions include_suppressed, which changes what tree is actually classified, leaving one parameter 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?

Names a specific verb and resource ("classify the active model's kind") and enumerates the classification families (part, sheet metal, assembly, drawing), so the agent knows exactly what output to expect. It also distinguishes itself from the data-fetching siblings by naming get_model_info and list_features as upstream sources rather than substitutes.

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 an explicit trigger: "Use it before rebuilding or editing an unfamiliar model, to pick a workflow," plus the precondition (an open document) and the exception (skip the read when both model_info and features are passed). It stops short of naming a when-not-to-use case or an alternative classifier, but the situational guidance is concrete.

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