Skip to main content
Glama
Sign In
Fusion360 MCP Server

Fusion360 MCP Server

by forgemorrow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Shell Body

shell

Remove a top or bottom face from a solid body to hollow it out, creating an internal cavity with a defined wall thickness.

Instructions

Hollow out a body by removing a face

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
body_nameNo
thicknessYes
body_indexNo
face_selectionNotop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations indicate this is a mutable (readOnlyHint: false), non-idempotent, non-destructive operation, but the description adds minimal context—it implies removal of material but doesn't specify if this creates a shell-like structure or leaves the body open. No rate limits, auth needs, or detailed behavioral traits are disclosed.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action, making it easy to parse quickly.

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

Completeness2/5

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

For a 4-parameter mutation tool with no output schema and low schema coverage, the description is inadequate. It lacks details on parameter usage, expected outcomes, error conditions, and how it fits within the CAD modeling context provided by siblings.

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

Parameters2/5

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

With 0% schema description coverage for 4 parameters, the description fails to compensate. It mentions 'removing a face' which loosely relates to 'face_selection', but doesn't explain 'thickness', 'body_name', or 'body_index', leaving key inputs undocumented.

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 clearly states the action ('hollow out a body') and the method ('by removing a face'), which is specific and distinguishes it from siblings like 'extrude' or 'thicken_surface'. However, it doesn't explicitly differentiate from similar tools like 'split_body' or 'offset_faces' that might also involve body modification.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a solid body), exclusions (e.g., not for surfaces), or compare to siblings like 'create_hole' or 'offset_faces' for hollowing operations.

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