Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

get_solidworks_info

Reports SOLIDWORKS installation details, server version, settings, log file location, and any tool modules that failed to load, helping diagnose setup or loading issues.

Instructions

Report the SolidWorks installation, the server's version, the settings and log file it uses, and any tool modules that failed to load.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the content of the report (including failure information, which signals it is safe to call in a broken state) and 'Report' implies a read-only, side-effect-free operation, but it never confirms that explicitly, nor states whether a live SolidWorks connection or server session is required.

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 front-loaded sentence that enumerates every returned item with no filler or 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?

With no parameters, no annotations, and no output schema, the description has to describe the return payload — and it does, itemizing four categories of information. The only gap is the precondition for calling it (does it work when SolidWorks is not connected?), which matters for an environment-report 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 nothing beyond the schema to explain; baseline credit applies. The description correctly implies a parameterless global query with no scoping inputs.

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 verb 'Report' plus an enumerated set of resources — SolidWorks installation, server version, settings/log file location, and failed tool modules — makes the diagnostic nature unmistakable and separates it from document-oriented siblings like get_document_info. It stops short of a 5 only because it never explicitly contrasts itself with those siblings.

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: an agent can infer this is a troubleshooting/environment-inspection call, but there is no statement of when to reach for it (e.g., before diagnosing failures) nor any exclusion or named alternative.

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