Skip to main content
Glama

Make Assembly

make_assembly

Create an App::Part container that holds linked parts and returns its handle and name, so you can group components into an assembly.

Instructions

Create an App::Part container to hold linked parts. Returns {handle, name}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "make_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoAssembly
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-readOnly, non-destructive, closed-world write, so the safety profile is covered. The description adds the return shape {handle, name} and clarifies that a container (not geometry) is produced, but says nothing about whether an existing assembly is affected or what happens with workspace scoping.

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?

Two short sentences, front-loaded with the operation and immediately followed by the return contract. Nothing redundant or padded.

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

Completeness4/5

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

For a two-optional-parameter creation tool with no output schema, the description covers the essential: what is created and what is returned. Remaining gaps (name uniqueness, workspace default behavior) are minor for a simple container-creation call.

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?

Schema coverage is only 50%: workspace is documented in-schema, but 'name' has no description beyond a default of 'Assembly'. The description does not explain what the name parameter controls or whether names must be unique, so it fails to compensate for the coverage gap.

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?

States a specific verb ('Create') and resource ('App::Part container to hold linked parts'), which is more informative than the bare tool name. It implicitly distinguishes itself from part-creation siblings like make_body or add_part by scoping to an assembly container, though it never names those alternatives.

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 phrase 'to hold linked parts' implies this is the setup step before adding components, giving an agent enough to infer the workflow position. However, there is no explicit when-to-use guidance, no mention of prerequisites (document/workspace state), and no comparison against siblings like add_part or merge_assembly.

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