Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

export_flat_pattern_dxf

Export an active SOLIDWORKS sheet metal flat pattern to DXF, keeping cut outline and holes on layer 0 and bend lines/notes on layer BEND for clean cutting.

Instructions

Export the active sheet metal part's flat pattern as a DXF: outline and holes on layer 0, bend lines and bend notes (text) on their own layer BEND (so a cutting program can leave them out); layer 0 holds only what is cut. Forming tools are not drawn (a dimple leaves only the outline). The file is in the document's length unit (inches from an inch template; the file's $INSUNITS says which) unless dxf_unit asks for mm or inch: then the document's unit is switched for the export and put back. The part must be saved, and an existing file needs overwrite. Returns path, bytes, flat size, dxf_unit (the unit of the file's coordinates), bend_lines and bend_notes (how many are on layer BEND). SolidWorks marks the part modified.

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": {
      "filepath": "<filepath>"
    },
    "name": "export_flat_pattern_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit of the flat size (mm, cm, m, inch or ft)
dxf_unitNoUnit of the DXF file's coordinates (default: the document's length unit)
filepathYesWhere to write it, ending in .dxf
overwriteNoReplace an existing file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so: it discloses the layer layout, that forming tools are omitted, that dxf_unit temporarily switches and then restores the document unit, that the part must be saved, that existing files need overwrite, and that SolidWorks marks the part modified. Those side effects and prerequisites are exactly the kind of behavior structured data does not supply here.

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 primary purpose and layer contract are front-loaded, and the paragraph stays dense with information rather than filler. It is a long single block, and splitting the unit-switching caveat into its own sentence group would aid scanning, but every clause carries real content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a four-parameter export tool with no output schema: the description even enumerates what is returned (path, bytes, flat size, dxf_unit, bend_lines, bend_notes). Prerequisites, unit behavior, and omitted geometry are all covered, leaving nothing an agent would need to guess before calling it.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns more by explaining the consequence of dxf_unit — the document's unit is switched for the export and restored — and by tying the default to the document's length unit and $INSUNITS. The 'unit' parameter (flat size only, vs. file coordinates) is left to the schema to distinguish.

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 and resource ('Export the active sheet metal part's flat pattern as a DXF') and immediately defines the output's structure — outline and holes on layer 0, bend lines and notes on layer BEND. An agent can distinguish this from export_step/export_stl 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions: the part must be saved, an existing file requires overwrite, and it applies only to the active sheet metal part with a flat pattern. It also names the downstream consumer ('so a cutting program can leave them out'), which clarifies intent. It stops short of comparing against sibling export formats, so there is no explicit when-not-this-tool guidance.

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