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

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_loft

Loft a smooth solid between two or more closed sketch profiles, specifying them in order by name or index.

Instructions

Loft a smooth solid between profiles taken from a list of sketch indices/ names (>=2), in order. Each sketch should contain one closed profile.

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": {
      "sketches": "<sketches>"
    },
    "name": "fusion_loft"
  }
}

Input Schema

NameRequiredDescriptionDefault
sketchesYes
operationNonew

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/5.0
Behavior3/5

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

The description adds useful behavioral constraints beyond the sparse annotations: ordering matters, profiles must be closed, and the result is a smooth solid. However, it does not explain the behavior of the operation enum (new/join/cut/intersect) or what happens when a profile is open, leaving some behavioral ambiguity.

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?

Two short, front-loaded sentences with no filler. The required input rule is stated immediately after the verb, and the additional constraint is separated cleanly.

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?

The description covers the required parameter and core behavior, but with no output schema it leaves the operation parameter's effects and error/edge-case behavior unspecified. For a modeling operation, this is a meaningful gap.

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 carries the burden. It adds real meaning to 'sketches' (indices/names, >=2, in order, closed profiles), but it says nothing about the optional 'operation' parameter beyond its enum values, which the schema already provides.

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 uses a specific verb and resource: 'Loft a smooth solid between profiles taken from a list of sketch indices/names (>=2), in order.' This clearly differentiates it from other modeling operations like extrude, revolve, or sweep, and states the core input condition.

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?

It gives clear call context: require at least two sketches, pass them in order, and each sketch must contain one closed profile. It does not explicitly name alternatives or exclusions, so it stops 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.

Deploy Server

Other Tools