Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Suppress or Unsuppress Feature

suppress_feature
Idempotent

Suppress or unsuppress model features to turn off rebuild-breaking items without deleting them, targeting the active configuration or selected configurations.

Instructions

Suppress or unsuppress a feature of the active model; suppressed features stay in the tree but are not built.

Use it to turn off a feature that breaks the rebuild without deleting it. It acts in the active configuration only, unless configurations is "all" or a list of names. Needs: an open part or assembly. Changes: the feature's suppression state, and its children's. Returns: data with feature, requested, suppressed (read back in the active configuration; null when unreadable), was_suppressed and configurations (where it applied).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe feature. `name` is required; `suppress` defaults to on (pass false to unsuppress).

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 by disclosing that children's suppression state also changes, that the effect is scoped to the active configuration by default, that an open part or assembly is required, and what the readback fields mean including the null-when-unreadable case. This is genuinely useful behavioral context for a mutation tool whose annotations only say idempotent and non-destructive.

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 organized into use-case, scope, prerequisites, changes, and returns. Every clause carries information an agent needs; nothing is redundant padding.

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 prerequisites, cascade side effects, configuration scoping, and the return payload even though an output schema exists. For a mutation tool with nested parameters, this leaves nothing important unstated.

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 already 100%, so the schema carries the parameter documentation, including the suppress default and the configurations enum/list. The description reinforces the configurations scope rule but adds little syntax or format detail beyond what the nested schema already states.

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 pair (suppress/unsuppress) and resource (a feature of the active model), and immediately clarifies the distinction from deletion: suppressed features 'stay in the tree but are not built.' That contrast makes it separable from delete_feature without opening either 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 an explicit use case ('turn off a feature that breaks the rebuild without deleting it') and declares the configuration scope rule (active configuration by default, unless configurations is 'all' or a list). It does not name delete_feature directly as the alternative to consider, so the routing guidance is implied rather than spelled out.

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