Skip to main content
Glama

Shell Solid

shell_solid

Hollow a raw Part solid into a thin-walled shell by removing selected faces; specify wall thickness grown inward to keep outer dimensions.

Instructions

Hollow a raw Part solid into a thin-walled shell (thickness does the same for PartDesign bodies).

faces: NON-EMPTY list of faces to REMOVE (the openings) — f_* tags (preferred), 'FaceN', or 1-based ints. thickness: wall mm (> 0), grown INWARD so outer dimensions are kept.

The input is hidden. Returns {handle (starts 'shell_'), name, volume (mm^3), wall_thickness, removed_faces}. Raises on empty faces, thickness <= 0, a bad index, or an offset too large for a valid shell.

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": {
      "handle": "<handle>",
      "faces": "<faces>",
      "thickness": "<thickness>"
    },
    "name": "shell_solid"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoShell
facesYes
handleYes
thicknessYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the input is hidden, describes the return object including the `shell_` handle prefix and fields, and lists specific failure conditions (empty faces, thickness <= 0, bad index, offset too large). This gives an agent substantial behavioral context for a mutation tool.

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?

The description is front-loaded with the core operation, then documents the two key parameters and return/error behavior. Every sentence adds useful information without repetition or filler.

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?

There is no output schema, and the description fully explains the return shape and failure modes. Together with the parameter semantics and sibling differentiation, it contains what an agent needs to invoke the tool correctly.

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?

With only 20% schema description coverage, the description compensates well for the two critical parameters: `faces` explains accepted face identifiers and that listed faces are removed, and `thickness` explains units, positivity, and inward growth preserving outer dimensions. It does not add meaning for `handle`, `name`, or `workspace`, leaving some gaps.

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 a raw Part solid into a thin-walled shell. It explicitly differentiates itself from the sibling `thickness` tool, noting that `thickness` applies to PartDesign bodies instead.

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 provides clear conditions for the key inputs: faces must be a NON-EMPTY list of faces to remove, and thickness must be > 0. It names the related `thickness` tool for PartDesign bodies, but does not explicitly state when not to use this tool or name other alternatives.

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