Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

open_document

Opens a SOLIDWORKS file and makes it the active document, or brings an already-loaded file to the front. Use it to switch to a specific file by full path.

Instructions

Open a SolidWorks file and make it the active document. A file that is already loaded (in the background, or only as a component of an open assembly) is brought to the front instead. The result names the active document; it is an error if the file could not be made active.

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

Input Schema

NameRequiredDescriptionDefault
filepathYesFull path of the file to open

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the already-loaded/component case, states that the result names the active document, and declares the failure mode ('it is an error if the file could not be made active'). It stops short of covering side effects on the currently active document (e.g., unsaved changes) or unresolved references.

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?

Three tight sentences, front-loaded with the core action, then the edge case, then the result/error contract. No redundant wording or restatement of the tool name.

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?

For a one-parameter tool with no output schema, the description supplies both the return semantics (names the active document) and the error contract, which is what an agent needs. The remaining gap is the effect on any previously active document, which matters for a tool that mutates session state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter exists and the schema already documents it at 100% coverage ('Full path of the file to open'), so the description adds no meaning beyond the schema. Baseline 3 is appropriate; nothing about path format, relative paths, or supported extensions is clarified.

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 ('Open a SolidWorks file') plus the resulting state ('make it the active document'), which is enough to distinguish it from siblings like list_open_documents, close_document, and save_document without opening any schema.

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 clause about already-loaded files being brought to the front is useful behavioral context, but it is not framed as when-to-use guidance and no alternative tool (e.g., listing or activating an already-open document) is named. Usage is implied rather than prescribed.

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