Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Export Image

export_image
DestructiveIdempotent

Save an image of the active SolidWorks model as PNG or JPG at a chosen standard view and size to show results or verify shape after changes.

Instructions

Save a picture of the active model in a standard view, as PNG or JPG, at a chosen size.

Use it to show a result, or to check a model's shape after a change. The view is set first (front, back, left, right, top, bottom, isometric, dimetric, trimetric, or current to keep the user's view). Needs: an open, active document. Changes: writes the image file, and turns the model to the view asked for. Returns: data with file_path, format, dimensions (the size written), requested_dimensions and view.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe image. `file_path` (or `output_path`) is needed; the format follows its extension. `width`/`height` (or `resolution` as "1920x1080") and `view_orientation` (isometric) have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag non-read-only, destructive and idempotent, and the description adds the crucial side effect that the model's view is changed to the requested orientation, plus the active-document requirement. It does not disclose what the destructive flag actually means in practice — whether an existing file at file_path is overwritten — which is the main remaining behavioral gap.

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?

Front-loaded with the purpose, then cleanly labeled 'Needs / Changes / Returns' blocks, so an agent can scan preconditions and side effects quickly. The Returns sentence largely restates the output schema and adds little on its own.

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 destructive write with nested parameters and an output schema, the definition covers precondition, side effects (including the view change) and result shape. The missing piece is the destructive/overwrite semantics and any permission or path-validity requirement, which matter most for a tool annotated destructiveHint=true.

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%, so the baseline is 3; the description does add some meaning by explaining the alias pairs (file_path or output_path, width/height or '1920x1080' resolution) and that the image format follows the file extension. However, it never mentions the alias fields by name or clarifies precedence when both format and format_type are supplied, leaving the alias ambiguity to the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Save a picture of the active model') plus the view/size/format scope, which lets an agent separate it from the vector-format siblings such as export_step or export_pdf. It falls short of a 5 because it says 'as PNG or JPG' while the schema's format_type also permits bmp and tiff, a small mismatch that could mislead about outputs.

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 clear positive use cases ('show a result' or 'check a model's shape after a change') and a hard precondition ('Needs: an open, active document'). It stops short of naming when not to use it (e.g. for vector/CAD export or batch runs via batch_export), so routing to alternatives is left implicit.

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