Skip to main content
Glama

cad_feature

Sweep, loft, fillet, chamfer, or pattern geometry to derive new solids from existing entities.

Instructions

Sweep, loft, fillet, chamfer or pattern geometry.

聚合特征操作。按 ``action`` 派发:sweep / loft / fillet / chamfer /
pattern_linear / pattern_circular / pattern_mirror。
- ``sweep`` / ``loft``: create new solids from a profile (sweep along a
  ``path``) or between ``profile_ids`` (loft). OCCT-backed when the
  ``occ`` extra is installed, with analytic fallbacks otherwise.
- ``fillet`` / ``chamfer``: round or bevel edges — exact on the OCCT
  kernel, otherwise report ``requires_occ``.
- ``pattern_linear`` / ``pattern_circular`` / ``pattern_mirror``: copy an
  entity into an array (rigid transforms, available on every kernel).

When not to use: ``cad_feature`` derives new geometry from existing
entities. For editing a single object's parameters use ``cad_object``
(update/transform); for boolean combination use ``cad_object``
(action=boolean).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureYesFeature action to perform, discriminated by `action`: sweep, loft, fillet, chamfer, pattern_linear, pattern_circular or pattern_mirror.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of created instances
actionYesFeature action executed
statusYesOperation status
messageNoStatus description
object_idNoResult object id
object_idsNoResult object ids
Behavior4/5

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

Annotations provide no hints (readOnly, idempotent, destructive all false), so the description carries the transparency burden. It discloses OCCT backends with fallbacks, exactness on OCCT kernel, `requires_occ` reports, and rigid transform patterns. It does not specify side effects on source entities, but the 'creates new geometry' phrase implies non-destructive behavior, which is useful.

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 well-structured: summary, Chinese translation, action-specific bullets, and a 'When not to use' section. It is front-loaded and avoids fluff, though the bilingual repetition is slightly redundant. Overall, every sentence earns its place.

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?

Given the tool's complexity with seven distinct actions, the description covers each action's behavior, kernel dependencies, fallbacks, and usage boundaries. The output schema also exists, so return-value details are not needed. The description is complete enough for correct tool selection and invocation.

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 coverage is 100%, so baseline is 3. The description adds value by mapping actions to the key parameters (`path`, `profile_ids`, `entity_id`, `radius`, etc.) and clarifying semantics like 'rigid transforms' and 'available on every kernel.' It does not duplicate schema text but provides high-level behavioral meaning per action.

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 clear summary, 'Sweep, loft, fillet, chamfer or pattern geometry,' listing all supported actions. It further distinguishes from sibling tools via the 'When not to use' section, naming cad_object for parameter edits and boolean operations. This fully satisfies purpose clarity.

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?

The description includes an explicit 'When not to use' section that names alternative tools and usage contexts, such as cad_object for update/transform and boolean. It also clarifies kernel-dependent behavior for each action group, giving the agent clear guidance on when each action is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tianshang301/TianshangCAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server