Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

screenshot

Save a PNG/JPG/TIF image of the current SolidWorks part or assembly from a specified view or zoomed region, omitting reference planes unless requested.

Instructions

Save a screenshot of the current part or assembly (PNG/JPG/TIF).

view: 'iso' (default), 'front', 'back', 'left', 'right', 'top' or 'bottom'; or from_dir = [x, y, z], the direction to look from, e.g. [-1, 1, -1] to see from behind and below what iso hides (the model's +y stays up). Zoomed to fit, or onto a detail: zoom_mm = [[x1, y1, z1], [x2, y2, z2]], the corners of the region to fill the image (model mm, in any view). Reference planes and axes are left out, so they do not cut through the shape; show_planes=True keeps them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
viewNoiso
zoom_mmNo
from_dirNo
show_planesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.13.0
    • addedInput schema / properties / from_dir
      Added value: +{
+  "anyOf": [
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "From Dir"
+}
    • addedInput schema / properties / show_planes
      Added value: +{
+  "default": false,
+  "title": "Show Planes",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.9.0
    • addedInput schema / properties / view
      Added value: +{
+  "default": "iso",
+  "title": "View",
+  "type": "string"
+}
    • addedInput schema / properties / zoom_mm
      Added value: +{
+  "anyOf": [
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Zoom Mm"
+}
  3. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses useful defaults (iso view, planes/axes omitted unless show_planes=True) and parameter behaviors, but omits operational details such as required active document, file overwrite behavior, and error conditions.

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 purpose and then systematically explains each option. Every sentence adds useful information without redundancy.

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?

Given no annotations and no output schema, the description covers most parameter and behavioral aspects needed to invoke the tool. However, the missing path explanation and lack of document-state prerequisites leave minor gaps.

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 description coverage is 0%, so the description must compensate. It provides detailed semantics for view, from_dir, zoom_mm, and show_planes, but does not describe the required 'path' parameter at all, leaving a notable gap.

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 ('Save a screenshot') and resource ('current part or assembly'), including output formats (PNG/JPG/TIF). No sibling tool provides screenshots, so it is uniquely identifiable from the list.

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?

The description clearly indicates the context (current part or assembly) and details how to control the view, but does not explicitly state when to use this tool versus alternatives or any exclusions. Since no alternative screenshot tool exists among siblings, the context is sufficient.

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