Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Move Body

move_body

Translate and rotate a named body in Fusion 360 using axis/pivot rotation and X/Y/Z translation, with lengths in cm and angles in degrees.

Instructions

Move a named body: optional rotation (angle, degrees) about an axis parallel to x/y/z through (pivot_x, pivot_y, pivot_z), then translation by (x, y, z). Unless a parameter says otherwise, lengths and coordinates are in cm (not mm) and angles in degrees.

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": {
      "body_name": "<body_name>"
    },
    "name": "move_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zNo
axisNoz
angleNoRotation in degrees (right-hand rule about +axis)
pivot_xNo
pivot_yNo
pivot_zNo
body_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare it as a non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the rotation-then-translation ordering, the pivot-based rotation model, the right-hand axis convention, and a units caveat (cm and degrees rather than mm). It stops short of saying what happens on an unknown body name or whether the move is undoable.

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 sentences, front-loaded with the verb and resource, then the operation sequence, then the units contract. Every clause carries information; no filler.

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

Completeness4/5

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

For a 9-parameter mutation tool with no output schema, the description supplies the geometric semantics and unit conventions an agent needs to call it correctly. Remaining gaps are modest: error behavior for a missing body name, default behavior when only body_name is supplied, and interaction with any design history.

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

Parameters4/5

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

Schema description coverage is only 11% (only 'angle' is documented), so the description must compensate. It does well: it explains that x/y/z are a translation, that pivot_x/y/z define the rotation point, that axis is the rotation axis, and that lengths are in cm while angles are in degrees. Defaults and the required body_name remain undocumented.

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+resource ('Move a named body') and details the two composed operations (rotation about a pivot axis, then translation), which cleanly separates it from scale_body and mirror without naming them. It lacks explicit sibling disambiguation, but the operation semantics are unambiguous.

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?

Usage is implied by the operation description (use to reposition/rotate an existing body), but there is no guidance on when to prefer this over mirror, scale_body, or pattern tools, nor any prerequisites (does the body need to be a standalone body vs a component?).

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