Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Shell

create_shell

Hollow the active solid part to a specified wall thickness by opening selected faces, ideal for boxes, housings, and cups.

Instructions

Hollow the active part to a wall thickness, opening the faces picked.

Use it for boxes, housings and cups: pick the face to open with a point on it (mm). It fails when the volume doesn't change. Needs: an open part with a solid body. Changes: adds a Shell feature. Returns: shell with name, thickness_mm, faces_removed, and volume_before, volume_after and volume_change (mm³).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe shell. `thickness` (mm) is required; `faces` lists a point on each face to remove; `outward` puts the wall outside.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses prerequisites, a failure mode (no volume change), and the side effect (adds a Shell feature). The annotations already establish that the tool is not read-only, not idempotent, and not destructive, so this added operational context is meaningful.

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 front-loaded and well structured with clear sections for usage, requirements, changes, and returns. The return-field list is somewhat redundant because an output schema exists, but the rest is efficient.

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 nested input object with full schema coverage and an output schema, the description covers purpose, prerequisites, failure behavior, side effects, and output fields. An agent has enough context to call this tool correctly.

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%, so the schema already documents thickness, faces, and outward. The description reinforces that faces are points in mm used to open the shell, but adds little semantic detail beyond the structured schema.

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 states a specific verb and resource: "Hollow the active part to a wall thickness, opening the faces picked." It also names concrete use cases (boxes, housings, cups), which makes the operation distinguishable from generic create tools.

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 usage context and prerequisites: use for boxes/housings/cups, pick a face with a point, and the part must be an open solid body. It also states a failure condition, but does not name alternatives or explicit when-not-to-use cases.

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