Skip to main content
Glama
shimmerjordan

self-host-fusion360-MCP

fusion_box

Create a cuboid box with width, depth, and height dimensions, centered on the XY origin and extruded in the positive Z direction. Automatically creates a document if none is open, and supports building inside a specified component.

Instructions

Create a box (cuboid): width(X) x depth(Y) x height(Z) in mm, centered on the XY origin and rising in +Z. Auto-creates a document if none is open. For a cube, pass equal width/depth/height. Pass component (a component name from fusion_create_component) to build the box INSIDE that component — useful for building assembly parts to then joint together.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
nameNo
depthYes
widthYes
heightYes
componentNo
Behavior4/5

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

The description adds behavioral context beyond annotations by stating that it auto-creates a document if none is open and that the box is centered on the XY origin rising in +Z. Annotations indicate mutability and side effects, and the description complements them without contradiction.

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 concise at three sentences, starting with core functionality and adding useful tips without extraneous information. Every sentence adds value and improves clarity.

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?

While the description covers orientation, auto-document creation, and component usage, it omits explanations for parameters 'x', 'y', and 'name', and does not specify the result (e.g., body or feature). Given the complexity of 7 parameters and no output schema, more detail is needed for full completeness.

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?

With 0% schema description coverage, the description partially compensates by explaining width, depth, height as dimensions and the 'component' parameter for assembly use. However, it does not clarify the purpose of parameters 'x', 'y', and 'name', leaving gaps in parameter understanding.

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 it creates a box (cuboid) with specific dimensions and orientation, differentiating it from shape tools like cylinders or spheres. The verb 'Create' and resource 'box' are precise and unambiguous.

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?

The description provides context for when to use the tool, such as building assembly parts inside a component and the shortcut for cubes. However, it does not explicitly state when not to use it or mention alternative tools, so it aligns with 'clear context, no exclusions'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shimmerjordan/self-host-fusion360-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server