Skip to main content
Glama

cad_assembly

Destructive

Create and manage mechanical assemblies: add parts, constrain with mates, solve constraints, generate BOMs, and create exploded views.

Instructions

Create, edit, solve or analyze an assembly.

聚合装配操作。按 ``action`` 派发:create / add_part / add_subasm /
add_mate / remove_part / solve / bom / explode。
- ``create``: initialize the document's assembly container.
- ``add_part`` / ``add_subasm``: build the tree; parts may reference a
  document ``entity_id`` and nest under a ``parent_id``.
- ``add_mate``: constrain two nodes (coincident / concentric / parallel /
  perpendicular / distance / angle).
- ``solve``: apply mates in order and return every node's world transform.
- ``bom``: flattened bill of materials (``format`` json or csv).
- ``explode``: radial offsets by tree depth (``direction`` x/y/z).

When not to use: ``cad_assembly`` composes *parts*, not geometry. Create
part geometry first with ``cad_object`` (create), then add it to the
assembly. For drawings of an assembly use ``cad_drawing``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assemblyYesAssembly action to perform, discriminated by `action`: create, add_part, add_subasm, add_mate, remove_part, solve, bom or explode.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bomNoBOM rows
csvNoCSV text when requested
nameNoAssembly / node name
actionYesAssembly action executed
statusYesOperation status
mate_idNoMate identifier
messageNoStatus description
node_idNoAssembly node identifier
recordsNoExploded positions
mate_typeNoMate type
mate_countNoNumber of mates solved
part_countNoTotal number of parts
transformsNoWorld transform of every node
assembly_idNoAssembly identifier
Behavior4/5

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

Annotations declare destructiveHint=true, and the description does not contradict it. The description adds meaningful behavioral context beyond annotations, such as 'solve applies mates in order and returns world transforms' and 'explode uses radial offsets by tree depth'. However, it does not explicitly warn about destructive or irreversible aspects of remove_part, leaving that to the schema.

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 well-structured with a bulleted action list and a clear 'When not to use' section. Each line is concise and informative, with no filler. The length is appropriate for a multi-action tool and the most important information is front-loaded.

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?

The description covers all eight actions, gives usage guidance, and clarifies the tool's role relative to siblings. The rich schema and output schema cover parameter details and return values. The description is fully adequate for an agent to select and invoke this tool correctly.

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, but the description adds value by explaining the purpose of key actions and their parameters (e.g., 'bom format json or csv', 'explode direction x/y/z'). It complements rather than repeats the schema, so a 4 is warranted.

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 'Create, edit, solve or analyze an assembly' – a specific verb+resource statement. It then enumerates each action (create/add_part/solve/etc.), and differentiates from sibling tools by stating it composes parts rather than geometry. This clearly establishes the tool's scope and unique purpose.

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?

An explicit 'When not to use' section tells the agent to use cad_object for geometry creation first and cad_drawing for drawings. The action list also implies the intended workflow (create assembly → add parts/mates → solve). This is exemplary usage guidance.

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