Skip to main content
Glama
andrewbartels1

SolidworksMCP-python

exit_sketch

Exit sketch editing mode to return to the 3D modeling environment, enabling creation of 3D features like extrusions and revolves.

Instructions

Exit sketch editing mode.

Exits the current sketch editing mode and returns to the 3D modeling environment. This is required after completing sketch geometry before creating 3D features like extrusions, revolves, or sweeps.

Returns: dict[str, Any]: A dictionary containing the resulting values.

Example: ```python # Complete sketch workflow await create_sketch({"plane": "Top"}) await add_circle({"center_x": 0, "center_y": 0, "radius": 5})

                result = await exit_sketch()
                if result["status"] == "success":
                    print("Sketch completed, ready for 3D operations")
                    # Now ready for extrude, revolve, etc.
                ```

            Note:
                - Must be called after sketch geometry creation
                - Required before executing 3D modeling operations
                - Automatically validates sketch geometry
                - Previous sketch remains selectable for feature creation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Without annotations, the description carries full burden. It discloses that it exits editing mode, validates geometry, and makes the sketch selectable for features. Could mention if there are side effects like discarding unsaved changes, but overall clear.

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?

The description is well-structured with a clear opening, an example, and notes. It is slightly long due to the example, but each part adds value. No wasted words.

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?

Given no output schema, the description explains return type and shows example result usage. It also notes that sketch remains selectable. This is complete for a simple exit action.

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?

There are no parameters, and schema coverage is 100%. The description does not need to add meaning beyond schema. Baseline of 4 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?

The description clearly states 'Exit sketch editing mode' with a specific verb-resource pairing. It distinguishes from siblings by explaining that it returns to the 3D environment and is required before 3D features like extrusions, which no other sibling 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 Guidelines5/5

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

The description explicitly states when to use: 'Must be called after sketch geometry creation' and 'Required before executing 3D modeling operations.' It also implies alternatives by noting it's necessary before other tools like create_extrusion,create_revolve, etc.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrewbartels1/SolidworksMCP-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server