Skip to main content
Glama
Sign In
solidworks-mcp

solidworks-mcp

by rdolan5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

solidworks_cam_connect

Destructive

Attach to the installed SOLIDWORKS CAM add-in and retrieve its API. Optionally specify a GUID or ProgID. Verify add-in presence separately from API/license availability using the returned status.

Instructions

Attach to the installed SOLIDWORKS CAM add-in and GetCWApp API. Optional exact GUID/ProgID. Add-in presence is distinct from API/license availability; inspect returned status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solidworks_cam_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations include destructiveHint=true, and the description does not contradict it, but it also does not explain what destructive side effects might occur from attaching. It does add the useful distinction between add-in presence and API/license availability, which is beyond the annotations, so some credit is given.

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 concise sentences with the primary purpose front-loaded and a caveat following. No redundant wording; every clause earns its place.

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?

With an output schema present, return details need not be described. The description covers the essential distinction between add-in presence and API availability, which is critical for correct usage, making it sufficiently complete for a single-parameter connection tool.

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 0% and the description explicitly explains the single optional parameter as 'exact GUID/ProgID', providing meaning the schema lacks. This compensates well for the absence of schema descriptions.

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?

The description clearly states the tool attaches to the SOLIDWORKS CAM add-in and GetCWApp API, which is a specific verb-resource pair. It distinguishes from the general solidworks_connect by naming the CAM add-in, though it does not explicitly contrast with that sibling.

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?

The description provides a caution about add-in presence versus API availability but gives no explicit guidance on when to use this tool versus alternatives like solidworks_connect or solidworks_cam_status. No when-to-use or when-not-to-use conditions are stated.

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