Skip to main content
Glama
fusion-cam

fusion-cam

cam_status

Inspect the active document's CAM state read-only, including setups, stock, operations, tools, toolpath validity, NC programs, generation jobs, and crash details; optionally check toolpaths.

Instructions

CAM state of the active document. Read-only; lengths in mm.

Setups (WCS, stock offsets, stock box in WCS mm, model size), operations with strategy, tool (number, type, diameter mm), toolpath present/valid, errors/warnings and checkToolpath (check=true), NC programs, running generation jobs, and last_crash (op and step) if Fusion crashed in a call.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNo
timeout_sNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does real work: it declares the operation read-only, fixes units to mm, states that toolpath validation is triggered by check=true, and warns that last_crash indicates Fusion crashed during a call. It omits cost/latency implications (a toolpath check on a large job) and any timeout behavior despite exposing timeout_s.

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?

Two compact sentences with the key constraints (read-only, mm) front-loaded before the content list. The long parenthetical enumeration is dense but each item adds information; nothing is redundant with the title or name.

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?

An output schema exists, so return-value documentation is not strictly required, yet the description still gives a useful inventory of the reported fields. For a read-only status tool this is close to complete; the only real gap is the unexplained timeout_s and the lack of any guidance on when the more expensive check=true should be disabled.

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 0%, so the description must compensate for both parameters. It explains the effect of check=true (adds checkToolpath validity results) but says nothing about timeout_s or its default of 60 seconds, leaving the caller to guess what happens on timeout and how that interacts with the heavier check path.

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?

Opens with a specific verb-less but precise statement: 'CAM state of the active document', then enumerates exactly what state is covered (setups, operations, tools, toolpaths, NC programs, jobs, last_crash). This clearly separates it from siblings like cam_machining_time or status, though 'state' alone would be vague without the enumeration.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for inspecting current CAM setup/operation/toolpath state before acting. There is no explicit 'use this when...' guidance and no exclusion or routing to alternatives such as cam_list_tools or cam_list_strategies, which overlap on the tool/strategy information this tool also returns.

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