Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

export_step

Export the active SOLIDWORKS part or assembly to a STEP file for other CAD programs, using AP214 to keep colors or AP203 without them; reports file size and body/component counts.

Instructions

Export the active part or assembly as a STEP file (.step / .stp) for other CAD programs. protocol AP214 (the default) keeps colours; AP203 does not. The document is not saved, renamed or changed. Reports the file size and how many solid bodies and components the file holds.

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_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYesWhere to write it, e.g. C:\Work\door.step
protocolNoSTEP application protocolAP214

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the source document is not saved, renamed or changed (non-destructive export) and that the response reports file size plus solid-body and component counts. It omits what happens if the target filepath already exists and any permission or open-document requirements.

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 front-loaded sentences: purpose and format, protocol choice, then side-effect guarantees and return summary. Every sentence adds information and nothing is padding.

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?

For a two-parameter export tool with no output schema, the description covers purpose, format choice, side effects and a return summary, which is close to what an agent needs. The one gap is overwrite/existing-file behavior, a realistic concern for a tool that writes to a caller-supplied path.

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 the baseline is 3, but the description adds genuine meaning beyond the schema by explaining the practical consequence of each enum value (AP214 preserves colours, AP203 does not), which the schema's 'STEP application protocol' label does not.

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 part or assembly as a STEP file') plus the concrete file extensions, so an agent can distinguish it from export_stl, export_pdf and export_flat_pattern_dxf by output format alone.

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?

'for other CAD programs' gives the intended context for using this over other export tools, and the description explicitly tells the agent which protocol to pick and why (AP214 keeps colours). It stops short of naming alternatives or stating exclusions, so it is clear context rather than full when/when-not 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