Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Create CAM Setup

cam_create_setup

Create a CAM manufacturing setup for a body, defining its stock, coordinate system, and operation type (milling, turning, or cutting).

Instructions

Create a manufacturing setup for a body. Defines the stock, coordinate system, and operation type (milling/turning/cutting). Unless a parameter says otherwise, lengths and coordinates are in cm (not mm) and angles in degrees.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body_name": "<body_name>"
    },
    "name": "cam_create_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSetup name
body_nameYesBody to machine
stock_modeNorelative_box
operation_typeNomilling
stock_offset_topNoTop offset (cm)
stock_offset_sidesNoSide offset (cm)
stock_offset_bottomNoBottom offset (cm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds useful behavioral context about unit conventions (cm and degrees unless stated otherwise) and clarifies what the setup defines, but does not disclose what happens on repeated calls, whether existing setups are modified, or any permission requirements.

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?

Three sentences, front-loaded with purpose and followed by unit conventions. The middle sentence about stock, coordinate system, and operation type is slightly redundant with the purpose but still adds useful detail without bloat.

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?

For a 7-parameter mutation tool with no output schema, the description covers purpose and unit semantics but leaves gaps in workflow context, return values, and behavior relative to sibling CAM tools. It is adequate but not fully complete for an agent navigating CAM operations.

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 coverage is 71%, and the description adds a global unit convention that applies across parameters, which is valuable beyond the schema's per-parameter hints. However, it does not explain the stock_mode options or add meaning to the enum parameters beyond restating the operation_type choices.

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 ('Create') and resource ('manufacturing setup for a body'), and lists what it defines (stock, coordinate system, operation type). It distinguishes this from sibling CAM tools only implicitly through the resource, not by explicitly naming alternatives like cam_create_operation.

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?

The description offers no guidance on when to use this tool versus alternatives such as cam_create_operation or cam_list_setups. There is no explicit when/when-not, nor any mention of prerequisites or typical workflow context.

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