Skip to main content
Glama
solidworks-mcp

solidworks-mcp

rename_feature

Rename a feature or sketch in the active SolidWorks part to give the model tree readable names and meaningful dimension labels.

Instructions

Renames a feature or sketch of the active part (e.g. "Boss-Extrude1" -> "Base plate"), so the tree is readable and dimensions get meaningful names (D1@Base plate).

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>",
      "new_name": "<new_name>"
    },
    "name": "rename_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
new_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds a real behavioral fact beyond them: renaming a feature also renames dependent dimensions (D1@Base plate) and is scoped to the active part. It does not mention failure behavior such as a missing name or duplicate-name collisions, which keeps it short of a 5.

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?

A single front-loaded sentence with the verb and resource first, followed by an illustrative example that earns its place. The parenthetical dimension-name example is slightly dense but adds concrete value rather than filler.

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?

Output schema exists so return values needn't be described, and annotations carry the mutation profile; the description covers scope (active part) and a key side effect. Only the failure modes and name-resolution rules are missing, which is minor for a two-parameter tool.

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 coverage is 0% and the two parameters are bare ('name', 'new_name'), so the description must compensate. The embedded example does clarify the semantics of both fields (existing tree name vs. new label), but it does not say whether the name is a bare tree name or a full identifier, or whether sketches and features share a namespace.

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?

States a specific verb (Renames) and resource (a feature or sketch of the active part) with a concrete before/after example ("Boss-Extrude1" -> "Base plate"). It is distinguishable from siblings like edit_feature or delete_feature, though it doesn't explicitly name an alternative.

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?

Usage is only implied through the benefit ("so the tree is readable and dimensions get meaningful names"), which tells the agent why to call it but not when to prefer it over edit_feature. No exclusions, prerequisites, or ordering guidance are given.

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