Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Shell Solid

shell_solid

Hollow a solid into a thin-walled shell: remove selected faces as openings, set wall thickness, and keep outer dimensions.

Instructions

Hollow a raw Part solid into a thin-walled shell (the direct-shape counterpart to thickness, which only works on PartDesign bodies).

handle: handle of the solid to hollow (e.g. a box/cylinder from add_primitive, or any shaped Part::Feature). faces: NON-EMPTY list of the faces to REMOVE — these become the shell's openings. Each entry is a face tag (f_..., from list_faces/query_faces, preferred and edit-stable), a 'FaceN' string, or a 1-based integer index. thickness: wall thickness in mm, must be > 0. The wall is grown INWARD, so the part's outer dimensions are preserved.

The consumed input solid is hidden (its geometry now lives in the shell). Returns {handle (starts 'shell_'), name, volume (mm^3 of the resulting walls), wall_thickness (mm), removed_faces (list of 1-based face indices that were opened)}. Raises if faces is empty, thickness <= 0, an index is out of range, or the offset is too large to produce a valid shell.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoShell
facesYes
handleYes
thicknessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description reveals key side effects beyond the annotations: 'The consumed input solid is hidden' and the wall 'is grown INWARD, so the part's outer dimensions are preserved.' It also lists error conditions and the return object's fields. This is thorough behavioral disclosure for a mutating 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 well-organized: a one-sentence purpose, a structured parameter list, then side effects, return value, and error conditions. Every sentence adds actionable information, and the key distinction from `thickness` is 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?

Despite having no output schema, the description documents the return shape, includes failure modes, and explains how faces should be referenced. Combined with the sibling distinction and parameter details, the agent has everything needed to invoke shell_solid 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 0% schema description coverage, the description carries the full burden for parameter semantics. It thoroughly explains `handle`, `faces` (including accepted tag formats and edit-stable preference), and `thickness` (units, sign, direction). The optional `name` parameter is not described, but it has a schema default and is self-explanatory, so this is a minor gap.

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 opens with a specific verb and resource: 'Hollow a raw Part solid into a thin-walled shell.' It also distinguishes itself from the sibling tool `thickness` by noting that thickness 'only works on PartDesign bodies,' so an agent can immediately tell when shell_solid is the intended choice.

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?

It explicitly names the alternative (`thickness`) and the condition that selects between them: shell_solid is the direct-shape counterpart while thickness only works on PartDesign bodies. This gives the agent concrete guidance on when to use this tool versus a closely related sibling.

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