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

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_split_body

Split a 3D body by a standard plane or another body to divide it into separate parts for further modeling.

Instructions

Split a body by a plane (xy/xz/yz) or by another body (tool_body).

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": "<body>"
    },
    "name": "fusion_split_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
planeNoxy
tool_bodyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations indicate readOnlyHint: false and destructiveHint: false, but the description does not clarify whether the original body is kept or replaced after split. No behavioral details beyond the basic operation are disclosed, leaving ambiguity about side effects.

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?

Single sentence of 15 words, front-loaded with action and split methods. No fluff, every word earns its place.

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 output schema and minimal annotations, the description omits crucial context: what happens after splitting (new bodies created? original removed?), prerequisites (body existence), and error conditions. Inadequate for a CAD operation.

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 coverage is 0%, so description must compensate. It adds meaning for 'plane' by listing xy/xz/yz options, but does not explain the 'body' parameter (what it refers to) or 'tool_body' (how it's used to split). Partial help, not full.

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 clearly states the verb 'Split' and resource 'body', and specifies the two splitting methods: by a plane or by another body. It distinguishes from sibling tools like fusion_split_face by explicitly mentioning body splitting.

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?

The description implies usage for splitting bodies via two modes but provides no explicit guidance on when to choose plane vs tool_body, nor does it mention alternatives or when not to use this tool. Sibling tools exist but no exclusions given.

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