Skip to main content
Glama
fusion-cam

fusion-cam

cam_list_strategies

Lists the operation strategies Fusion offers for a setup and returns strategy names to pass to cam_add_operation for adding machining operations.

Instructions

List the operation strategies Fusion offers for a setup (live; 55 milling strategies on 2706.1.17, e.g. face, adaptive2d, pocket2d, contour2d, drill, bore, chamfer2d, adaptive, parallel, scallop). Pass the 'name' to cam_add_operation.

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

Input Schema

NameRequiredDescriptionDefault
setupNo
timeout_sNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the list is 'live' and version-dependent ('55 milling strategies on 2706.1.17'), which warns the agent results may change across releases. It says nothing about caching, ordering, cost, or what the optional setup scope changes in the result, which is a meaningful gap for a zero-annotation tool.

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 action, then a compact parenthetical of examples that earns its space by helping the agent recognize strategy names. Only mild excess in the version/count aside.

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 values need not be described, and the downstream cam_add_operation link is covered. But for a 2-parameter tool with zero annotation and zero schema coverage, the undefined timeout and ambiguous setup semantics leave the definition short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across both parameters, so the description must compensate. It implies 'setup' scopes the strategy list but never explains the null/default behavior, and 'timeout_s' is left entirely 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 and resource ('List the operation strategies Fusion offers for a setup') and grounds it with concrete examples (face, adaptive2d, pocket2d, drill) plus a version marker. An agent can tell this enumerates strategy names rather than tools or setups, though it never explicitly contrasts itself with cam_list_tools.

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?

The closing instruction 'Pass the name to cam_add_operation' gives a clear downstream use, which is genuine routing value. However there is no guidance on when to prefer this over cam_list_tools, nor on whether omitting 'setup' is valid or what it returns in that case.

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