Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

delete_feature

Delete a named SOLIDWORKS feature, sketch, plane, or assembly mate; dependency checks block removal unless child deletion is enabled, and the result reports what was removed.

Instructions

Delete a feature, sketch or plane by name; in an assembly also a mate by name. Refused when other features depend on it unless delete_children is true. Reports everything that was removed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFeature name from list_features, e.g. 'Cut-Extrude1'
delete_sketchNoAlso delete the sketch the feature was made from
delete_childrenNoAlso delete the features that depend on this one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses the dependency-guard refusal behavior, the gating flag that overrides it, and that the result enumerates everything removed. It stops short of stating irreversibility/undo behavior or what happens to sketches by default.

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?

Three short clauses with the resource scope front-loaded and the refusal rule immediately after; no filler. Slightly dense semicolon chaining, but nothing that fails to earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers scope, the key failure mode, and result reporting for a destructive three-parameter tool with no annotations and no output schema. Gaps remain around sketch handling defaults and recovery from an accidental delete, which matter for an irreversible operation.

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%, so all three parameters are already documented, including the list_features provenance for name. The description only reinforces delete_children semantics and says nothing extra about delete_sketch, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (delete) and enumerates the resource types it accepts: feature, sketch, plane, and — in an assembly — a mate by name. That is far more precise than the name alone, though it overlaps with the sibling delete_mate without explaining the split.

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

Usage Guidelines3/5

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

Gives a real usage condition (refused when dependents exist unless delete_children is true), which tells the agent how to succeed. However, it never states when to prefer delete_mate versus this tool for mates, nor when to use delete_component instead, so sibling routing is left to inference.

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