Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Create CAM Operation

cam_create_operation

Add a machining operation to a Fusion 360 CAM setup by choosing a strategy; set tool, feeds, speeds, and geometry to generate the toolpath.

Instructions

Add a machining operation to a setup. Strategy determines the toolpath type. 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": {
      "setup_name": "<setup_name>",
      "strategy": "<strategy>"
    },
    "name": "cam_create_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOperation name
coolantNoflood
stepdownNoAxial depth of cut (cm)
stepoverNoRadial stepover (cm)
strategyYesMachining strategy
feed_rateNoFeed rate (cm/min)
setup_nameYesName of the parent setup
tool_numberNoTool number from library
spindle_speedNoSpindle speed (RPM)
tool_diameterNoNot supported — tool geometry comes from the CAM tool library; select via tool_number instead. Passing this raises an error.
geometry_face_indexNoIndex (0-based) of a face on the setup's model body whose outer loop becomes the operation's chain geometry — equivalent to clicking that face in the Fusion UI. Required for chain-based strategies (2d_contour, 2d_pocket, 2d_adaptive, drilling, bore, ...) to generate a toolpath; find face indices via get_object_info on the body.
tool_from_operationNoName of an existing operation whose real library tool should be reused, syncing the tool-search filter to match. tool_number alone only writes a parameter and leaves the operation without a tool — generating it then opens a modal dialog inside Fusion that freezes this connection until someone dismisses it by hand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent), so the description adds rather than carries this. It usefully discloses a cross-cutting behavioral convention (units in cm, angles in degrees) that is not derivable from the annotations, but omits workflow consequences such as needing a tool before toolpaths can be generated.

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?

Three short sentences, front-loaded with the core action and immediately followed by the two facts (strategy semantics, unit conventions) an agent most needs. No filler.

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 12-parameter mutation tool with no output schema, the description covers the essential unit convention, but the schema carries all critical gotchas (tool_number fallback, modal freeze, geometry_face_index requirements). The description itself leaves the workflow context — sequencing with toolpath generation — unstated.

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 description coverage is already 92%, so the baseline is 3. The description goes beyond the schema by stating the global unit convention for lengths, coordinates and angles, which disambiguates several numeric parameters whose schema notes are terse or absent.

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 and resource ('Add a machining operation to a setup') and clarifies the role of the strategy parameter. It is clear against generic siblings, though it never names or distinguishes itself from close CAM siblings like cam_create_setup or cam_generate_toolpath.

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?

There is no when-to-use guidance and no exclusions. It does not say that a setup must exist first, nor when to follow this with cam_generate_toolpath or cam_post_process, so the agent must infer the CAM workflow from sibling names alone.

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