Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

set_components_suppression

Apply the same suppression state to multiple components in a single call, reducing configuration switches for efficient BOM variant preparation.

Instructions

Cambiar el estado de varios componentes en una sola llamada.

Uso típico autopartes: preparación de variantes BOM ("suprime los 8 tornillos que el Base trim no incluye"). Más eficiente que un bucle sobre set_component_suppression — cuando config_scope es "all" o "specific", la implementación cambia de configuración una sola vez por config y aplica todos los componentes en ese contexto. [en: Apply the same suppression state to multiple components in one call. Typical use: trim-variant BOM prep — suppress N fasteners a Base trim doesn't include. Faster than looping set_component_suppression: switches config once per config_scope target instead of once per (component × config) pair.]

Args: component_names: List of SW component instance names from get_active_assembly_info. Must not be empty. All names are validated up-front; if any are missing the call raises before any change is made. state: "suppressed" | "resolved" | "lightweight". Default "suppressed". config_scope: "this" | "all" | "specific". config_names: Required when config_scope="specific".

Returns: Dict with count (number applied), state (the applied state), and components (list of {name, path, suppressed, state}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNosuppressed
config_namesNo
config_scopeNothis
component_namesYes
Behavior4/5

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

With no annotations, description covers up-front validation and early failure, config_scope batching behavior, and return structure. Lacks mention of authorization requirements or side effects like rebuilds, but sufficiently transparent for typical use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Bilingual and somewhat verbose, but front-loaded with purpose and efficiency. Could be trimmed to single language without loss, but still effective.

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, usage, parameters, behavior, and return type. No output schema, but return dict is described. Complete for a batch mutation tool with clear sibling differentiation.

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 0%, but description explains all four parameters: component_names source and validation rule, state enum, config_scope behavior, and config_names dependency. Adds value beyond bare 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?

Description clearly states it changes suppression state of multiple components in one call, with specific verb 'set' and resource 'components suppression'. Distinguishes from sibling set_component_suppression by noting efficiency gain.

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?

Explicitly recommends over set_component_suppression for multiple components and gives typical trim-variant BOM prep example. Does not explicitly state contraindications (e.g., single component) but implied by sibling existence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/solidworks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server