Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

delete_component

Deletes a top-level component from the active assembly, removes its mates, and reports deleted mates, remaining components, and new mate errors; refuses sub-assembly and pattern instances.

Instructions

Delete a top-level component from the active assembly. SolidWorks deletes the mates that use it with it; the result lists them (name and type), the components left, and any other mate that now has an error. A component inside a sub-assembly is refused (it belongs to the sub-assembly's file), as is an instance of a component pattern.

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": {
      "component": "<component>"
    },
    "name": "delete_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentYesTop-level component name from list_components, e.g. Bracket-2

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?

With no annotations, the description carries the full burden and does substantial work: it discloses the cascading side effect (SolidWorks deletes dependent mates) and enumerates what the result contains — deleted mate names/types, remaining components, and newly errored mates. It does not state permission requirements or irreversibility/confirmation needs, which keeps it short of a 5 for an unannotated mutation tool.

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?

Three sentences, all load-bearing: action first, then consequences and return contents, then refusals. Nothing is repeated from the schema and there is no filler.

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?

For a one-parameter mutation with no annotations and no output schema, the description covers the destructive side effects, the failure modes, and the shape of the return payload. An agent has everything needed to decide and invoke correctly.

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% and the single parameter already documents that it expects a top-level name from list_components with an example. The description adds no syntax, matching, or ambiguity-handling detail beyond what the schema states, so the baseline 3 applies.

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 with an explicit scope qualifier: "Delete a top-level component from the active assembly." The scope word "top-level" plus the refusal clause distinguishes it from destructive siblings like delete_feature and delete_mate.

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 concrete negative guidance: a component inside a sub-assembly is refused, and so is a pattern instance. That tells the agent when not to call and why, though it never names an alternative tool to use for those cases (e.g. a sub-assembly-aware deletion path).

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