Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

connect_solidworks

Attach to a running SOLIDWORKS session or launch the application automatically when none is open, establishing the connection your AI app needs to build models.

Instructions

Attach to the running SolidWorks, or start it first when none is running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses a side effect — that it will launch SolidWorks when nothing is running — but says nothing about licensing prompts, startup time, what happens on failure, whether the connection is persistent, or what the call reports back. For a process-launching tool with zero annotation coverage, this is a significant gap.

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?

A single sentence with zero filler, front-loading the primary action and appending the fallback condition. Nothing could be removed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter tool with no output schema, the description covers the core behavior and the important launch side effect. It still leaves the agent guessing about post-call state (is a session now guaranteed ready for subsequent SolidWorks calls?) and error behavior, which matters for a bootstrap-style 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?

The tool takes zero parameters, so there is no parameter semantics to convey and the baseline of 4 applies. The description correctly adds no parameter detail, keeping attention on the attach-versus-start behavior instead.

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 gives a specific verb and resource — 'Attach to the running SolidWorks' — and clarifies the dual mode (attach vs. start). It is clearly distinct from data-retrieval siblings like get_solidworks_info or setup siblings like solidworks_guide, though it never explicitly names or contrasts with them.

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

Usage Guidelines3/5

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

The condition for the fallback path is stated plainly ('when none is running'), which implies this is the entry point before other SolidWorks operations. However, there is no explicit 'use this before calling other tools' instruction and no named alternative for cases where a connection already exists or should be verified.

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