Skip to main content
Glama
fusion-cam

fusion-cam

cam_add_operation

Adds a machining operation to a Fusion CAM setup using a chosen strategy, tool, geometry, and parameters, returning parameter errors for invalid settings.

Instructions

Add an operation to a setup with a tool from cam_list_tools (made with Tool.createFromJson).

strategy: a name from cam_list_strategies (face, contour2d, pocket2d, adaptive2d, drill, ...). geometry, the selections a strategy needs: {"holes": {"diameter_mm": 16, "tol_mm": 0.01}} or {"holes": "all"}: hole faces for drill/bore; {"contour": "outline", "side": "outside"}: contour2d on the part's base silhouette (climb cut). params / params_json: Fusion parameter name -> value. Strings are expressions and LENGTHS NEED UNITS ('1 mm', '-0.5 mm'); bools become true/false; numbers are unitless. Verified names: contour2d bottomHeight_offset, doMultipleDepths, maximumStepdown; drill drillTipThroughBottom, breakThroughDepth, cycleType ("'drilling'", "'deep-drilling'"), incrementalDepth; any op tool_spindleSpeed, tool_feedCutting. tool_number: default reuses the number of the same tool, else the next free one (H/D offsets follow). Returns parameter_errors for any names that did not apply.

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": {
      "strategy": "<strategy>",
      "tool_id": "<tool_id>"
    },
    "name": "cam_add_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
setupNo
paramsNo
tool_idYes
geometryNo
strategyYes
timeout_sNo
params_jsonNo
tool_numberNo
allow_user_documentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses unit requirements ('LENGTHS NEED UNITS'), that strings are parsed as expressions, that bools/numbers are treated differently, that tool_number defaults to the same tool's number and offsets follow, and that parameter_errors is returned for names that failed. It does not describe permission needs, what happens if the referenced setup does not exist, or the effect of allow_user_document.

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 core action and its dependency are front-loaded in the first sentence, followed by a structured breakdown by parameter and concrete geometry examples. It is dense and slightly run-on in the params block, but nearly every clause conveys actionable detail rather than filler.

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?

For a 10-parameter mutation tool with an output schema, the description supplies the workflow, geometry shape examples, unit/expression rules, and the fact that parameter_errors is returned, which is enough to invoke it correctly. The unexplained setup/name/timeout_s/allow_user_document parameters and absent failure modes keep it from being fully complete.

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 0%, so the description must compensate, and it covers the two required parameters plus geometry, params, params_json, tool_number and the verified parameter names with types and value quirks. Four parameters (name, setup, timeout_s, allow_user_document) get no explanation, leaving a gap, but the high-value parameters are handled well beyond schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Add an operation to a setup') and immediately anchors the tool dependency ('a tool from cam_list_tools'), which distinguishes it from cam_create_setup and the list-strategy tools. An agent can tell exactly what this mutates without opening the schema.

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 establishes the required workflow context by pointing at cam_list_strategies for the strategy name and cam_list_tools for the tool, and it explains which geometry shapes pair with which strategies (drill/bore vs contour2d). It does not state explicit exclusions or when to prefer a different operation-creation path, so it stops short of a 5.

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