Skip to main content
Glama
Mesteriis

Plasticity MCP

plasticity_hollow_faces

Destructive

Remove selected faces from a solid and shell it with an inward or outward wall thickness in millimeters to create hollowed CAD geometry.

Instructions

Remove selected faces and shell a solid with an inward or outward wall thickness in millimeters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
intentNo
faceIdsYes
revisionYes
directionNoinward
wallThicknessMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare that this is a destructive, non-read-only operation, lowering the disclosure bar. The description adds useful context that selected faces are removed and that shelling can be inward or outward with millimeter thickness, but it does not cover revision handling, reversibility, or what happens to the removed faces.

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 definition is a single front-loaded sentence with no filler. It conveys the core operation and the key thickness direction concept efficiently.

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 destructive six-parameter solid mutation tool with no output schema and 0% schema description coverage, the description is incomplete. It omits the meaning of id and revision, intent behavior, and direction default, which an agent needs in order to invoke the tool safely and correctly.

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 0%, so the description must carry the burden. It clarifies the roles of faceIds, wallThicknessMm, and direction, but says nothing about id, revision, or intent, leaving three of six parameters without semantic guidance in either schema or description.

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 resource: removing selected faces and shelling a solid with inward or outward wall thickness. It is clear enough to distinguish from generic face deletion or thickening, but it does not explicitly name or differentiate from the closely related plasticity_hollow_solids or plasticity_thicken_faces siblings.

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?

There is no guidance on when to choose this tool versus alternatives such as plasticity_hollow_solids, plasticity_thicken_faces, or plasticity_offset_faces. The description only says what the operation does, leaving routing and prerequisites entirely to inference.

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