Skip to main content
Glama
Sign In
Fusion Native MCP

Fusion Native MCP

by Dawn-Of-Justice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_cam_parameters

Inspect CAM parameter names and expressions on any operation or setup to validate machining data in Fusion.

Instructions

Inspect installed CAM parameter names and expressions on an operation or setup.

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": {
      "document_id": "<document_id>",
      "cam_id": "<cam_id>"
    },
    "name": "fusion_cam_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
setupNo
cam_idYes
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral disclosure burden. 'Inspect' clearly signals a read-only operation, and 'names and expressions' indicates what the tool surfaces. However, it does not mention side effects, prerequisites, potential errors, or return shape, leaving some behavioral context implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence uses nine words to convey action, resource, and scope with no filler. Every word earns its place, and the structure is easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only context for correct invocation. It explains the core purpose but omits how the setup flag routes to an operation versus a setup, what the returned names-and-expressions mapping looks like, and any prerequisites. This leaves meaningful gaps for a 3-parameter tool.

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 description coverage is 0%, and there are 3 parameters, so the description needed to compensate. It only hints at the 'setup' boolean by saying 'operation or setup,' while document_id and cam_id remain semantically unexplained. This is insufficient for confident parameter construction.

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 states a specific verb ('Inspect') and a specific resource ('installed CAM parameter names and expressions') scoped to 'an operation or setup.' This clearly distinguishes it from mutation-focused siblings like fusion_set_parameter and from library-level tools like fusion_cam_inventory.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. It does not mention fusion_set_parameter for editing parameters, fusion_cam_inventory for inventory-level data, or any when-not-to-use condition. The phrase 'operation or setup' only scopes the target; it does not explain tool selection.

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

Deploy Server

Other Tools