Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Rename Feature

rename_feature
Idempotent

Rename a feature in the active part or assembly feature tree to give it a meaningful name. Rejects names already in use and keeps the current name if unchanged.

Instructions

Rename a feature in the active model's feature tree.

Use it to give features meaningful names (e.g. "MountingHoles"). The new name is read back: a name another feature already uses is an error. Renaming to the current name succeeds with no change. Needs: an open part or assembly. Changes: the feature's name. Returns: data with old_name, new_name, renamed and, when unchanged, reason.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe rename. `old_name` and `new_name` are required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the collision rule ("a name another feature already uses is an error"), the no-op case ("renaming to the current name succeeds with no change"), the document prerequisite, and what state changes. These are exactly the edge cases an agent must anticipate before invoking a mutation, and the annotations alone (readOnlyHint=false, idempotentHint=true) would not convey them.

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?

Front-loaded with purpose, then a labeled Needs/Changes/Returns block that is easy to scan. The Returns enumeration partially duplicates the existing output schema, so a sentence is spent on information already available in structured form.

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 single-parameter mutation with nested input, the description covers purpose, prerequisite, error condition, no-op behavior, and the effect on the model. Nothing an agent needs in order to call it correctly is missing, and return values are additionally backed by an output schema.

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 both nested fields carry their own examples (Fillet1 → MountingEdgeFillet), so the schema already does the work. The description adds only the return field names old_name/new_name, not new meaning about the inputs, 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+resource ("Rename a feature") plus the scope ("in the active model's feature tree"), which cleanly separates it from siblings like delete_feature, suppress_feature, and select_feature. No ambiguity about what the tool does.

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 a clear intended use ("give features meaningful names") and a hard prerequisite ("Needs: an open part or assembly"). It does not name alternatives or when-not conditions, but the operation is narrow enough that this is a minor gap.

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