Skip to main content
Glama

Make Body

make_body

Creates a PartDesign Body as a container for subsequent sketches and features, returning its handle and name for follow-up operations.

Instructions

Create a PartDesign Body. Subsequent sketches/features go inside it.

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_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBody
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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the return shape ({handle, name}), which is genuinely helpful given there is no output schema, but it omits prerequisites (active document/workspace, transaction context) and error behavior for a mutation tool.

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 action and scope, followed by the return shape. Nothing is wasted.

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

Completeness3/5

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

With no required parameters and no output schema, the description does cover the creation contract and return value. But for a mutation tool in a large modeling toolset it leaves out document/workspace preconditions and body-naming implications, which an agent needs to call it correctly.

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 description coverage is only 50%: 'workspace' is documented in the schema while 'name' (default 'Body') has no description at all. The description mentions neither parameter, so it does not compensate for the gap or explain what 'name' names.

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 and resource ('Create a PartDesign Body') and clarifies scope by saying subsequent sketches/features go inside it, which separates it from document-level tools like new_document or add_primitive. It does not explicitly name a sibling alternative, so it stops short of 5.

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?

'Subsequent sketches/features go inside it' implies workflow ordering (create the body before make_sketch/pad), which is useful implied usage. However, there is no explicit when-to-use/when-not guidance, no mention that a document or transaction must already be open, and no pointer to alternatives.

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