Skip to main content
Glama
fusion-cam

fusion-cam

cam_machining_time

Estimates cycle time in seconds for a CAM setup or operation, including feed/rapid distances, tool changes, and per-operation breakdown from generated toolpaths.

Instructions

Estimated cycle time in seconds for a setup or operation (default: the last setup), with feed and rapid distances in mm, tool changes and a per-operation breakdown. rapid_mm_min (mm/min) and tool_change_s are machine assumptions. Needs generated toolpaths.

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

Input Schema

NameRequiredDescriptionDefault
targetNo
timeout_sNo
rapid_mm_minNo
tool_change_sNo
feed_scale_pctNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the important behavioral trait that results depend on prior toolpath generation, and that rapid_mm_min/tool_change_s are machine assumptions rather than measured values. It does not state that this is a read-only/compute-only operation, nor what happens on timeout (timeout_s is unexplained) or when no toolpaths exist.

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?

Front-loaded with the primary result, then the returned data, then the parameter assumptions and the precondition. Three sentences with little waste; the only soft spot is that the parameter caveats are tacked on mid-sentence rather than grouped.

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?

An output schema exists, so return-value shape need not be re-explained, and the prerequisite is stated. However, for a 5-parameter tool with zero schema description coverage, the definition leaves meaningful gaps: timeout behavior, the meaning/units of feed_scale_pct, and error conditions when toolpaths are missing.

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 for all five parameters. It explains target semantics ("a setup or operation", default last setup) and defines two assumptions with units (rapid_mm_min in mm/min, tool_change_s), but timeout_s and feed_scale_pct are left completely undefined in both schema and description.

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?

States a specific verb+resource: it estimates cycle time for a setup or operation and enumerates the returned content (seconds, feed/rapid distances in mm, tool changes, per-operation breakdown). Scope is narrowed with a default ("the last setup") and a precondition ("Needs generated toolpaths"). It does not explicitly distinguish itself from siblings like cam_status or cam_generate, so it stops short of a 5.

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 implied rather than spelled out: "Needs generated toolpaths" tells the agent to run it after toolpath generation, and the default target tells it what happens when no setup/operation is given. There is no explicit when-not guidance or named alternative (e.g., when to use cam_status instead), leaving the agent to infer sequencing.

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