Skip to main content
Glama
solidworks-mcp

solidworks-mcp

edit_sketch

Reopens an existing SolidWorks sketch by name so you can modify it with sketch tools; close it with end_sketch to update dependent features.

Instructions

Reopens an existing sketch (name from get_feature_tree, e.g. "Sketch1") to change it with the sketch tools; a sketch already open is closed first. Close it with end_sketch: the features built on it then update.

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_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses two meaningful behaviors: reopening implicitly closes any currently open sketch, and the payoff of ending the sketch is that dependent features rebuild. That 'closing the open sketch first' side effect is genuinely useful state information an agent could not get from annotations, though permissions or model-state requirements are not covered.

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 dense clauses, front-loaded with the action, then the lifecycle (close with end_sketch and the resulting feature update). Slightly tangled punctuation (semicolon plus colon), but no sentence is 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?

For a one-parameter state-entry tool with annotations and an output schema, this covers action, prerequisite lookup, side effects, and exit path. The only gap is that it never says what happens to unsaved edits on the sketch it closes.

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 coverage is 0% and the single parameter is bare, so the description has to carry the load — and it does: it identifies the value's source (get_feature_tree) and gives a concrete format example ('Sketch1'). What is missing is any mention of case sensitivity, exactness, or error behavior when the name does not match.

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?

The description gives a specific verb+resource ('reopens an existing sketch ... to change it with the sketch tools') and names the sibling that supplies the identifier (get_feature_tree) and the companion close tool (end_sketch). It never explicitly contrasts itself with start_sketch or edit_feature, so the differentiation from siblings is inferred rather than stated.

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?

It gives clear operative guidance: obtain the name from get_feature_tree, then reopen the sketch and modify it with the sketch tools, then close it with end_sketch. It also warns that an already-open sketch is closed first. It stops short of stating when not to use this (e.g. creating a new sketch instead).

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