Fusion360 Live MCP

Overview Schema Source Related Servers Discussions Admin

Post Process

cam_post_process

Generate NC code (G-code) from Fusion 360 CAM toolpaths. Specify setup, post processor, and output folder to produce machine-ready code.

Instructions

Post-process toolpaths to generate NC code (G-code)

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>"
    },
    "name": "cam_post_process"
  }
}

Input Schema

Name	Required	Description	Default
`setup_name`	Yes	Setup to post-process
`output_units`	No		mm
`program_name`	No	NC program name/number written into the G-code header. Most posts (including fanuc) require a plain integer here and reject a text label	1001
`output_folder`	No	Output directory (default: ~/Desktop)
`operation_name`	No	Specific operation (omit to post all in setup)
`post_processor`	No	Post processor short name ('fanuc', 'grbl', 'haas') resolved against the local post folder when the Fusion build provides one, or a full path to a .cps file (required on cloud-post builds)	fanuc

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is partially covered. But the description adds nothing behavioral: it never mentions that the tool writes G-code files to disk (output_folder), what happens on repeat runs or whether existing output is overwritten.

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?

A single front-loaded clause with no filler or redundancy. It is tight, though the brevity contributes to the specification gaps noted elsewhere rather than being an independent virtue.

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

Completeness2/5

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

For a 6-parameter CAM operation with no output schema, the description omits prerequisites, the relationship to cam_generate_toolpath, and the fact that the operation produces files as side effects. An agent could invoke it correctly from the schema alone but lacks the workflow context.

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 description coverage is 83% with rich per-parameter notes (e.g., the fanuc integer-only program_name constraint, post-processor resolution rules), so the schema carries the semantic load. The description adds no parameter meaning beyond naming the G-code output, making the baseline 3 appropriate.

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 gives a specific verb+resource+result: post-processes toolpaths to produce NC code (G-code), which is clearly distinct from CAM siblings like cam_create_setup and cam_create_operation. It does not, however, differentiate itself from cam_generate_toolpath, which an agent could plausibly confuse it with.

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 guidance on when to use this versus cam_generate_toolpath, nor on prerequisites such as needing an existing setup with generated toolpaths. The only usage signal ('omit to post all in setup') lives in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server