Skip to main content
Glama
solidworks-mcp

solidworks-mcp

edit_feature

DestructiveIdempotent

Modify an existing extrusion or extruded cut by updating depth, end condition, direction, or second depth, then rebuild the model; only supplied values are replaced.

Instructions

Changes an existing extrusion or extruded cut (name from get_feature_tree) and rebuilds: depth_mm, end_condition (blind / through_all / midplane), reverse (direction), depth2_mm (second direction, 0 removes it). Only the values given are replaced. For other features change their dimensions with get_dimensions / set_dimension.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
reverseNo
depth_mmNo
depth2_mmNo
end_conditionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already disclose destructiveHint=true, idempotentHint=true and openWorldHint=false, so safety and idempotency are covered. The description still adds real value beyond them: it reveals that a rebuild is triggered and that the edit is a partial merge ("Only the values given are replaced"), which the annotations do not say. It does not mention permission requirements or what a failed rebuild leaves behind.

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, front-loaded with the action and scope, then the parameter semantics, then the routing exclusion. The parenthetical annotations on each parameter are terse and each one carries information that is not recoverable elsewhere.

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?

An output schema exists, so return values need no prose, and the definition is otherwise sufficient to call the tool correctly. The remaining gap is small: it does not say what a caller should expect when the edit invalidates downstream features or when the named feature is not an extrusion.

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 description coverage is 0%, so the description carries the full burden and largely does: it explains reverse as direction, depth2_mm as the second direction with the non-obvious rule that 0 removes it, and enumerates the end_condition values. The only parameter not explained is the required "name", whose role is only implied by the get_feature_tree parenthetical.

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 ("Changes an existing extrusion or extruded cut") and scopes it precisely with the origin of the identifier ("name from get_feature_tree"). It also distinguishes itself from the dimension-editing siblings by declaring that non-extrusion features belong elsewhere.

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

Usage Guidelines5/5

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

Explicitly names the alternative path for out-of-scope features ("For other features change their dimensions with get_dimensions / set_dimension"), giving a clear when-not-to-use rule plus the tool to use instead. Nothing about 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.