Skip to main content
Glama
Sign In
CAD-CAE-Agent SolidWorks MCP Server

CAD-CAE-Agent SolidWorks MCP Server

by caoguanqiu1-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

convert_file_format

Convert SolidWorks files between formats such as STEP, IGES, STL, and PDF to share models with other CAD and review tools.

Instructions

Convert a SolidWorks file from one format to another.

Supports exporting source files to target formats such as STEP, IGES, STL, PDF, or other adapter-supported conversion outputs.

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": "convert_file_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe input data value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only mentions 'exporting source files' but omits details like side effects (e.g., file overwriting), permission requirements, or whether the operation is a read or write. This is insufficient for safe agent decision-making.

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?

Two sentences, front-loaded with purpose ('Convert a SolidWorks file from one format to another'), no filler. Efficient and easy to parse.

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?

Despite output schema existing, the description lacks context about required sub-parameters (source_file, target_format) and optional ones like units and quality. For a tool with nested parameters and no annotations, this is insufficiently complete.

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 coverage is 100% with descriptions for all parameters, so description adds no extra meaning beyond schema. Baseline of 3 is appropriate as the schema already documents each parameter adequately.

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 'Convert a SolidWorks file from one format to another' and lists supported formats (STEP, IGES, STL, PDF). This distinguishes it from sibling export tools that target a single format, making the purpose specific and clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus sibling export tools like export_step or export_iges. The description does not specify prerequisites or scenarios where this generalized conversion is preferable.

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