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

self-host-fusion360-mcp

by mystify59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_export_dxf

Export a sketch to 2D DXF format for laser cutting and CAD drawings. Converts sketch geometry into a DXF file ready for external use.

Instructions

Export a sketch to a 2D DXF file (e.g. for laser cutting / drawings).

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": {
      "sketch": "<sketch>"
    },
    "name": "fusion_export_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
sketchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/5.0
Behavior2/5

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

Annotations indicate it's not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds no further behavioral details such as file overwrite behavior, path handling, or side effects beyond stating the export action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one short sentence) and front-loaded with essential information. However, it is slightly too brief, missing details that could be added without sacrificing conciseness.

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 2 parameters, no output schema, and moderate complexity (file export), the description is incomplete. It does not explain file save location, return value, or prerequisites like a valid sketch. More context is needed for an agent to use it effectively.

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

Parameters1/5

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

Schema description coverage is 0%, and the description only mentions 'sketch' without explaining that it's a required parameter expecting an ID or name. The 'path' parameter is entirely undocumented. No parameter semantics are conveyed beyond the raw schema.

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?

Description clearly states 'Export a sketch to a 2D DXF file' with an example use case (laser cutting/drawings). It distinguishes itself from sibling export tools by specifying 2D DXF format and application.

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 laser cutting or 2D drawings but does not explicitly state when to use this tool over other export siblings (e.g., fusion_export_stl, fusion_export_step). No exclusion criteria or alternatives are mentioned.

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