Skip to main content
Glama

Thickness

thickness

Hollow a solid into a shell by setting wall size and open faces; choose inward or outward growth, join, and mode to create controlled cavities in mechanical parts.

Instructions

Hollow out a solid into a shell.

base: handle of the body's tip feature (the solid to hollow). open_faces: list of {handle, face: tag|'FaceN'} that become the shell's openings. thickness: wall thickness (mm). reversed: True (default) grows the wall INWARD into the solid (the natural "hollow this part" interpretation). False grows outward. join: 'Arc' | 'Intersection'. mode: 'Skin' | 'Pipe' | 'RectoVerso'.

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

Input Schema

NameRequiredDescriptionDefault
baseYes
joinNo
modeNo
nameNoThickness
reversedNo
thicknessNo
workspaceNoRun this call in this named workspace
open_facesYes

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds useful behavioral meaning: open_faces become shell openings, reversed=True grows inward by default, and join/mode options affect construction. It still does not state whether the original solid is replaced or whether the operation can fail on invalid open faces.

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 compact and front-loads the core operation before listing parameter meanings. Each line adds information, though the parameter block could be organized slightly more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no output schema, the description covers the important geometric semantics well. It is incomplete on usage routing versus siblings and does not clarify return behavior or failure conditions, leaving meaningful gaps for an agent.

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 description coverage is low at 13%, so the description carries most of the parameter explanation. It meaningfully defines six core parameters, including the handle-based base, open_faces structure, thickness in mm, reversed direction semantics, and join/mode enum values. It omits only name and workspace, which are less central to the operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and transformation: 'Hollow out a solid into a shell.' That is clear enough for an agent to understand the operation. However, it does not distinguish this tool from the sibling shell_solid, which likely has overlapping purpose.

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

Usage Guidelines2/5

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

The description explains parameters but does not say when to use this tool versus shell_solid, pocket, or other modeling siblings. There are no explicit preconditions, exclusions, or alternative-routing instructions.

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