Skip to main content
Glama
Sign In
self-host-fusion360-mcp

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_sweep

Sweep a closed profile sketch along an open path sketch's first curve to create a solid or surface.

Instructions

Sweep a profile (from profile_sketch) along the first curve of path_sketch. Draw the path as an open sketch (line/arc/spline) and the profile as a closed sketch, then sweep.

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": {
      "profile_sketch": "<profile_sketch>",
      "path_sketch": "<path_sketch>"
    },
    "name": "fusion_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
operationNonew
path_sketchYes
profile_sketchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.7/5.0
Behavior4/5

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

The description adds useful behavior beyond the annotations by stating that only the first curve of path_sketch is used and that the path/profile sketch types have specific shape requirements. It does not contradict the provided annotations.

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?

The description is two focused sentences with no filler. It leads with what the tool does and then supplies the prerequisite sketch setup, earning every word.

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?

For a 4-parameter mutation tool with no output schema, the description is adequate for the default 'new' operation but incomplete for the other operation modes and the optional profile parameter. It also does not say what the result of the sweep will be or whether existing geometry will change.

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?

The description gives meaning to the two required parameters by tying profile_sketch to the profile and path_sketch to the path. However, schema description coverage is 0%, and the description does not explain the optional 'profile' parameter or the 'operation' enum, leaving those to inference.

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?

The description clearly states the action: sweep a profile from profile_sketch along the first curve of path_sketch. It is unambiguous about the resource and operation, though it does not explicitly differentiate itself from related feature tools like extrude, loft, or revolve.

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?

It gives concrete setup instructions: the path must be an open sketch and the profile must be a closed sketch. However, it does not explain when to choose sweep over alternatives, nor does it mention exclusions or failure conditions.

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