nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

shell

Hollow out a solid body to create walls of a specified thickness, and remove selected faces to open the cavity for NX model edits.

Instructions

Hollow out a solid body leaving walls of the given thickness. Faces listed in remove_faces are opened. Units: millimetres (mm) and degrees.

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

Name	Required	Description
`body`	No	Body to shell. Optional when the part has exactly one body.
`thickness`	Yes	Wall thickness (mm).
`remove_faces`	No	Faces. Each item is either a face id from list_faces (e.g. "F:B1:2"), an object {"near": [x, y, z], "body": "B1"?} (closest face), or {"normal": [x, y, z], "body": "B1"?} (the outermost planar face whose outward normal points in that direction, e.g. [0,0,1] = top face).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the core geometry change and units, but does not explain whether the original body is modified in place, what happens if thickness exceeds geometry limits, permission or error behavior, or what the operation returns.

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 front-loaded and compact, with the core operation stated first. The units sentence is mostly useful, though degrees are irrelevant to the available shell parameters, which is a minor inefficiency.

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 a three-parameter CAD mutation with no annotations and no output schema, the description covers the core operation and parameter meaning adequately because the schema is fully documented. However, it lacks behavioral context about in-place modification, failure conditions, and return behavior that would help an agent invoke it confidently.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents body, thickness, and remove_faces in detail. The description adds unit information and clarifies that listed faces are opened, but does not add meaning beyond the schema's parameter documentation, making the baseline 3 appropriate.

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 uses a specific verb and resource: 'Hollow out a solid body' with wall thickness. It clearly distinguishes shelling from sibling operations such as create_hole or boolean_subtract by explaining that walls remain and selected faces are opened.

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 implies when to use the tool through its core purpose, but it does not explicitly state when to choose shell versus alternatives like create_hole or boolean_subtract. It also gives no prerequisites or exclusions, leaving usage guidance only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.