Skip to main content
Glama
solidworks-mcp

solidworks-mcp

activate_document

Idempotent

Brings an open SolidWorks document to the front and makes it active by title, file name, or full path, so subsequent commands operate on the intended document.

Instructions

Makes an open document the active one (brings its window to the front), by title, file name or full path as shown by list_open_documents. Every other tool works on the active document.

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": {
      "name": "<name>"
    },
    "name": "activate_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare it non-read-only, idempotent and non-destructive; the description adds the crucial global side effect that all other tools operate on whichever document is active, which is not derivable from the annotations. It does not say what happens on a failed match (error vs. no-op), leaving one behavioral 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?

Two sentences, zero filler. The primary action and its effect are front-loaded, and the disambiguating detail about accepted name forms and the pointer to list_open_documents follow in the right order.

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?

An output schema exists, so return values need no explanation, and the description covers action, effect, name formats, and downstream consequence. Only failure/ambiguity handling is unaddressed, which is a minor omission for a one-parameter 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 description coverage is 0% and the single parameter is just 'name', so the description carries the burden — and it does, explaining that the value can be a title, file name, or full path, and that list_open_documents shows valid values. It stops short of addressing ambiguity such as duplicate titles.

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 ('Makes an open document the active one') plus the concrete effect ('brings its window to the front'). The reference to list_open_documents and the note that every other tool operates on the active document make it unmistakable against siblings like open_document or close_document.

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

Usage Guidelines4/5

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

It gives a clear selection rationale: use this to set which document subsequent tools act on, and it points to list_open_documents as the source of valid names. There is no explicit 'when not to use' or fallback behavior if the named document is not open, which keeps it below a 5.

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