Export a Fusion 360 design or selected body to an STL file for 3D printing, with adjustable refinement and a custom save path.
Export to STL (for 3D printing). Optional body (else whole design);
refinement low/medium/high. Saved on the host (default ~/fusion-mcp-exports).
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| path | No | ||
| refinement | No | medium |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate mutability (readOnlyHint=false) and potential side effects (openWorldHint=true). Description adds that it saves to the host with a default path, but does not explain file overwrite behavior or require an open document, leaving gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no fluff. Essential info is front-loaded: purpose, optional body, refinement options, and save location. Every word counts.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description should cover the return or outcome. It states the file is saved, which is helpful, but does not mention what the tool returns (e.g., success message, path). It is adequate but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate. It explains 'body' and 'refinement' well, but 'path' is omitted. This partial coverage results in a baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Export to STL (for 3D printing)', which is a specific verb and resource. It distinguishes from sibling export tools like export_dxf and export_f3d by format and purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Mentions optional 'body' parameter to select a specific part, otherwise exports the whole design, and refinement levels. Does not explicitly compare with other export tools, but the context of 3D printing makes it clear when STL is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.