Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Export Flat Pattern

export_flat_pattern
DestructiveIdempotent

Export the active sheet-metal part's flat pattern to DXF or DWG for laser or waterjet cutting, writing only the outline without bend lines or sketches.

Instructions

Export the active sheet-metal part's flat pattern to DXF or DWG, for laser or waterjet cutting.

It writes the flat outline only, without bend lines or sketches. A part with no sheet-metal body is not_found and nothing is written. Needs: an open, active sheet-metal part. Changes: writes the file, replacing one already there. Returns: data with file_path and size_bytes.

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": {
      "input_data": "<input_data>"
    },
    "name": "export_flat_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe export. `file_path` (ending in .dxf or .dwg) is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations that mark it as non-read-only, destructive, and idempotent, the description explains exactly what is written: the flat outline only, without bend lines or sketches. It also discloses the overwrite behavior, the no-write failure case, the prerequisite active sheet-metal part, and the returned fields.

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 front-loaded with the core action and format, then uses compact labeled clauses for requirements, side effects, and return values. Every sentence contributes useful information without repetition.

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?

For an export operation with one required nested parameter and an output schema, the description covers the prerequisite state, output content limitations, overwrite behavior, failure semantics, and return summary. Nothing essential for correct invocation is missing.

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%, and the nested file_path parameter is already documented as requiring a .dxf or .dwg extension. The description adds useful context about what the export represents, but does not add parameter-level meaning beyond the 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?

The description states a specific verb and resource: export the active sheet-metal part's flat pattern to DXF or DWG. It distinguishes the operation from general exports by specifying flat-pattern-only output for laser or waterjet cutting.

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?

It gives clear usage context: the part must be open and active, and the flat pattern is intended for laser or waterjet cutting. It also states the failure case when no sheet-metal body exists, though it does not explicitly name when to use a different export tool instead.

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