Skip to main content
Glama
fusion-cam

fusion-cam

cam_post

Post-process Fusion CAM setups or operations to G-code using a named post, save .nc files, and return paths, line counts, and initial lines for verification.

Instructions

Post-process to G-code; returns the .nc paths, line counts and the first head_lines lines.

post: a post from Fusion's library by name ('fanuc.cps') or a system:// URL. targets: setup/operation names (default: all operations of the last setup), which need valid toolpaths. output_dir default: /test_output/nc. split: 'auto' posts one program, but Fusion for Personal Use refuses tool changes in one program, so it then writes one program per tool (_01_T1.nc, ...; run them in order); 'tool' always splits; 'none' fails instead. Files Fusion writes to its default NC folder are moved to output_dir. A bad adsk.cam call can crash Fusion: if status reports last_crash, do not repeat that call unchanged.

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": "cam_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNofanuc.cps
setupNo
splitNoauto
targetsNo
filenameNo
timeout_sNo
head_linesNo
output_dirNo
program_nameNo1001
allow_user_documentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and delivers: it discloses that files Fusion writes to its default NC folder get moved, that 'none' fails, that Personal Use refuses tool changes and triggers per-tool splitting with ordered filenames, and that a bad adsk.cam call can crash Fusion. Missing are permission/auth requirements and any idempotency or repeat-run behavior.

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?

The purpose and return values are front-loaded in the first sentence, then parameters are addressed in a compact run. It is dense but nearly every clause carries operational information; the split explanation is the longest and is justified by its non-obvious behavior.

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?

This is a complex, side-effecting ten-parameter tool with no annotations, and the description covers failure modes, defaults and side effects adequately; an output schema exists so return values need not be explained further. The remaining gap is the batch of undocumented parameters and how setup interacts with targets.

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 0%, so the description must compensate, and it does for post (name or system:// URL), targets, output_dir default and split semantics. It leaves setup, filename, timeout_s, program_name and allow_user_document entirely undefined, so roughly half of the ten parameters remain opaque.

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 first clause is a specific verb+resource: 'Post-process to G-code', with the return shape named ('.nc paths, line counts and the first head_lines lines'). It is distinguishable from siblings like cam_generate because it clearly describes the posting step, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a real prerequisite — targets 'need valid toolpaths' — and explains default scoping ('all operations of the last setup'), which tells an agent when it can call without args. It stops short of explicit when-to-use/when-not guidance or naming the sibling that produces the toolpaths first.

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