Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

shell

Hollows out a solid body to create walls of a specified thickness, with optional openings defined by face points, normals, or current selection.

Instructions

Hollow out the body, leaving walls of the given thickness. The openings are the faces given by open_faces (points on them) and / or open_normal; with neither, the faces currently selected are removed, and with nothing selected the body becomes a closed hollow.

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": {
      "thickness": "<thickness>"
    },
    "name": "shell"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
outwardNoAdd the wall outside the body instead of inside
thicknessYesWall thickness
open_facesNoModel points on the faces to remove
open_normalNoRemove every flat face with this outward normal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the default/fallback behavior when no opening inputs or no selection exist, but omits whether the operation mutates the body in place, whether it is reversible, and what errors occur (e.g., thickness too large for the body).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the core action front-loaded and the opening-selection fallback chain following immediately. Every clause adds semantic information; there is no 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 five-parameter geometric mutation with no annotations and no output schema, the description covers the essential semantics of the openings and defaults. It falls short only on mutation/error behavior, which an agent would benefit from knowing.

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 100%, so baseline is 3; the description goes beyond the schema by explaining the interaction and precedence between open_faces and open_normal and what happens when both are absent. It does not elaborate on 'outward' or 'unit', but the schema already documents those.

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 and resource ('Hollow out the body') plus the resulting geometry ('leaving walls of the given thickness'). This is a distinct CAD operation that cannot be confused with sibling tools like chamfer_edges or create_sketch_on_face.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description explains the opening-selection logic (open_faces, open_normal, fallback to current selection, fallback to closed hollow), which is effectively guidance on how to invoke it in different situations. However, it gives no explicit when-to-use versus alternative guidance or prerequisites such as needing an active part document.

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