Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Activate Document

activate_document
Idempotent

Make an already-open SolidWorks document the active one so subsequent tools act on it. Match it by window title, full path, or file name.

Instructions

Make an already-open document the active one, so the next tools act on it.

Match it by window title, full path or file name (not case-sensitive); see list_open_documents. To open a file that isn't open yet, use open_model. Needs: the document open in SolidWorks. Changes: the active document. Returns: data with activated (the title) and verified (read back from SolidWorks; null when it couldn't be read). No match is an error that lists the open documents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_data": "<input_data>"
    },
    "name": "activate_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe document. `title_or_path` is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description reinforces this with explicit 'Needs:' and 'Changes: the active document' statements plus the no-match error behavior. It also explains the `verified` read-back semantics, which is genuine added context, but the presence of annotations covering the safety and idempotency profile keeps this at a solid 3 rather than higher.

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?

Front-loaded action sentence, then match modes, then an alternative route, then compact Needs/Changes/Returns blocks. Every sentence carries distinct information; nothing is redundant with the schema or annotations.

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

Completeness5/5

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

Precondition, side effect, error case, sibling routing and return fields are all covered, so nothing needed to invoke it correctly is missing. The return description is a bonus given an output schema already exists.

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 100%, so the baseline is 3, but the description adds real meaning: matching accepts window title, full path or bare file name and is explicitly case-insensitive, which the schema does not state. Minor residual gap is whether partial matches are accepted or only exact ones.

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?

States a specific verb and resource — make an already-open document the active one — and immediately frames the consequence ('so the next tools act on it'). This cleanly separates it from list_open_documents (discovery) and open_model (opening a not-yet-open file).

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

Usage Guidelines5/5

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

Explicitly names the alternative for the adjacent case: 'To open a file that isn't open yet, use `open_model`,' and points to `list_open_documents` for finding a target. The precondition 'the document open in SolidWorks' further constrains when this applies.

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