Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_status

Checks whether SolidWorks is running and reports the active document and entity count to verify connection status before CAD operations.

Instructions

检查 SolidWorks 连接状态:是否在运行、当前文档、实体数量。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the returned fields, implying a non-mutating read, but it never states what happens when SolidWorks is not running — an error response versus a status flag is left ambiguous — nor does it mention side effects, timeouts, or whether calling it launches or attaches to the application.

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 compact sentence, front-loaded with the core action and followed by the exact information returned. There is no filler, no restatement of the tool name, and nothing that could be trimmed.

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 zero-parameter tool with no annotations and no output schema, the description should fully explain the return shape and the disconnected-state behavior. It lists three fields but omits the failure case (not installed, not running, no document open) and does not say whether the entity count is model-wide or per-configuration, leaving a real gap for a status probe.

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 the baseline is 4; there is nothing for the description to clarify beyond the schema, and it adds no misleading parameter hints.

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 uses a specific verb+resource pair (检查 SolidWorks 连接状态) and enumerates the returned information: running state, current document, entity count. That distinguishes it from all listed siblings, which are action tools (export, save, hole, plate) rather than status probes, though the description never explicitly contrasts itself with any of 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?

Usage is only implied: it is implicitly a pre-flight check before other SolidWorks operations, but the description never states when to call it, whether prerequisites exist (e.g., SolidWorks installed/running), or what alternative to use if it reports disconnected. No exclusions or routing guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.