Skip to main content
Glama
fusion-cam

fusion-cam

import_step

Imports a STEP file into a new scratch Fusion design, reports body count plus bounding box and volume, and optionally checks dimensions against expected values.

Instructions

Import a STEP file (e.g. exported from Inventor) into a NEW Fusion design marked as scratch.

Units are millimetres. path: absolute path to a .step/.stp file. Returns the document name, body count, per-body and overall bounding box (mm) and volume (mm^3). Optional check: expected_size_mm=[L, W, H] and/or expected_volume_mm3, compared within tolerance_pct (default 0.1 %). Sizes are compared sorted (axis-agnostic) and a warning says if the axes differ (e.g. a Y-up vs Z-up export). Refuses while Fusion is mid-command. Only documents created here can be closed later with close_scratch. If the call times out it may still finish inside Fusion: call status and inspect before retrying, or you get a second document.

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": {
      "path": "<path>"
    },
    "name": "import_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
timeout_sNo
tolerance_pctNo
expected_size_mmNo
expected_volume_mm3No

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses side effects (creates a NEW document), the scratch marking, the mid-command refusal condition, and the non-idempotent timeout hazard ('it may still finish inside Fusion ... or you get a second document'). It also states the return contents and the close_scratch eligibility rule.

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 purpose and free of filler, with each sentence carrying distinct information. The single dense paragraph packs units, return values, tolerance checking, refusal behavior, and timeout recovery together, which is efficient but slightly hard to scan.

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

Completeness5/5

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

For a mutation tool with no annotations, five parameters, and real duplicate-document risk, the description covers creation semantics, units, validation options, failure modes, and cleanup path. Return values are restated even though an output schema exists, which is redundant but harmless.

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

Parameters5/5

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

Schema coverage is 0%, and the description compensates for every parameter: path is an absolute path to a .step/.stp file, units are millimetres, expected_size_mm is given as [L, W, H] and compared axis-agnostically with a Y-up/Z-up warning, expected_volume_mm3 is in mm^3, tolerance_pct defaults to 0.1%, and timeout_s is implied by the timeout behavior.

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?

States a specific verb and resource ('Import a STEP file ... into a NEW Fusion design') plus the distinguishing scope detail that the result is a scratch document. It also names close_scratch as the paired lifecycle tool, so an agent can place it among siblings 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?

Gives concrete operating conditions: refuses while Fusion is mid-command, and on timeout it directs the agent to 'call status and inspect before retrying' rather than blindly re-running. It lacks an explicit when-not-to-use statement (e.g. other import paths or formats), which keeps it just 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.