Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

shell_part

Hollow out a solid body to a specified wall thickness, leaving selected faces as openings for housings or enclosures.

Instructions

Vaciado de pared (shell) — hollow out the body, optionally removing the listed faces to leave openings.

selector (recommended) — pick the open face(s) by INTENT, e.g. leave the top face open: selector={"filter": {"geom": "planar", "normal_axis": "+z"}}. Same face-selector schema as create_sketch_on_face (filter geom/body/normal_axis/axis/area, sort, pick). May match several faces (each becomes an opening). Mutually exclusive with face_centroids_mm.

Junior workflow: "haz un vaciado de 2mm dejando la cara superior abierta" — common for cast housings (carcasas), plastic enclosures (gabinetes), and any hollow case with an opening. SolidWorks shells the entire body to the given wall thickness; faces listed in face_centroids_mm become open holes.

Args: thickness_mm: Espesor de pared (wall thickness) in mm. Must be positive and less than half the smallest body dimension — SW silently rejects thicknesses too large to fit. face_centroids_mm: Faces to leave open. Pass a list of [x, y, z] centroids from list_faces(). None or [] = closed shell (the whole body hollowed, no openings). Each centroid must match a real face within 0.01 mm. outward: False (default) puts the shell wall INSIDE the original surface — the standard "hollow housing" intent. True keeps the shell outside (offset surface outward) — rare; only for special cases.

Returns the new Vaciado feature (type=shell, D1=thickness_mm).

Caveat: shell is destructive of subsequent face-anchored sketches — faces shift to the new offset surfaces. Run shell_part LATE in the feature tree, after all face-anchored boses/cuts are placed.

Example — 2mm-walled cup, 50×50×40 mm with the top open: create_sketch("front") create_rectangle(0, 0, 50, 50) extrude_sketch(40) faces = list_faces() top = max( (f for f in faces if f["normal"][2] > 0.9), key=lambda f: f["centroid_mm"][2], ) shell_part(2.0, face_centroids_mm=[top["centroid_mm"]])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outwardNo
selectorNo
thickness_mmYes
face_centroids_mmNo
Behavior5/5

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

Discloses important behavioral traits: destructiveness to subsequent face-anchored sketches, SolidWorks silent rejection of thickness too large, outward parameter effect, return value format. Since no annotations exist, the description carries full burden and meets it thoroughly.

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?

Well-structured with purpose, detailed args, caveat, and example. Some redundancy (bilingual title) and verbosity, but information is effectively organized and front-loaded.

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?

Covers all aspects: purpose, parameters with constraints, behavioral caveats, usage timing, and a concrete example. No output schema exists, but return value is explained. Complete for a complex shell operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description adds complete meaning: thickness_mm (positive, < half smallest dimension), face_centroids_mm (from list_faces, exact match), selector (face-selector schema, mutually exclusive), outward (default inside). Compensates fully for missing schema descriptions.

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 the tool's function: 'Vaciado de pared (shell) — hollow out the body, optionally removing the listed faces to leave openings.' It specifies the verb (hollow out) and resource (body), and distinguishes it from siblings by focusing on shell operations with face removal options.

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?

Provides explicit usage contexts: common for cast housings, plastic enclosures, and hollow cases. Advises to run shell_part late in the feature tree to avoid destructiveness. Does not explicitly state when not to use, but the guidance is clear and sufficient.

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/danielproxd2/solidworks-mcp'

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