Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Export View Sheet

export_view_sheet

Render orthographic and isometric PNG views into a shareable HTML sheet for mechanical engineers, then restore the viewport camera afterward.

Instructions

Render canonical orthographic + isometric views as PNGs and emit a self-contained HTML sheet suitable for sharing with a mechanical engineer. Opens in any browser; Print -> Save as PDF for a static artifact. Restores the viewport camera after rendering.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_view_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFree-form notes rendered below the views. Newlines preserved; HTML is escaped.
titleNoHeading shown on the sheet (default: document name).
viewsNoOrdered list of views to render (default: iso, front, top, right).
image_sizeNo[width, height] in pixels (default [1200, 900]).
output_dirNoDestination folder (default: ~/Desktop/<doc>_views_<timestamp>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the write nature is partly covered there. The description adds genuinely new context beyond annotations: the artifacts produced (PNGs + self-contained HTML), that it opens in any browser, and the notable side effect that it 'Restores the viewport camera after rendering' — an important state-restoration disclosure.

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?

Three tight sentences with the core output front-loaded, followed by consumption instructions and the side-effect note. No filler, and the most decision-relevant information (what is produced and how it is shared) comes first.

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?

With no output schema, the description does carry the burden of describing returns and does so well (PNGs plus a self-contained HTML artifact, browser-viewable, PDF-convertible). The viewport-camera restoration side effect is also covered, leaving only minor gaps such as naming/location of produced files, which the output_dir default in the schema partly addresses.

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 100%, so every parameter (notes, title, views, image_size, output_dir) is already documented with defaults and semantics. The description only alludes to 'canonical orthographic + isometric views' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb pair ('Render ... and emit') with the exact resource: orthographic + isometric views as PNGs plus a self-contained HTML sheet. This is clearly distinguishable from siblings like render_view (single render) and export_stl/export_step (single-format geometry exports) without opening any schema.

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 gives context ('suitable for sharing with a mechanical engineer', 'Print -> Save as PDF') which implies the sharing/documentation use case, but never says when to choose this over render_view, export_stl, or export_step, and offers no exclusions or prerequisites.

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