Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Get File Properties

get_file_properties
Read-onlyIdempotent

Retrieve active document file details—name, path, size, dates, type, configuration, and unsaved changes—to check status before saving or closing.

Instructions

Deprecated: use get_model_info.

Report the active document's file details: name, path, size, dates, type, configuration and unsaved changes.

Use it to check what is open and whether it has unsaved changes before saving or closing. For the model itself (rebuild status included), use get_model_info; for custom properties, use get_custom_properties. Needs: an open, active document. Read-only. Returns: properties with file_name, file_path, file_size_bytes, created_date and modified_date (Unix timestamps; empty for a document never saved), document_type, configuration, is_dirty and feature_count.

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_file_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds the deprecation status, the active-document prerequisite, and the semantic detail that date fields are empty for a document never saved. These are meaningful operational details beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The deprecation warning is front-loaded, followed by purpose, usage, alternatives, prerequisites, and return semantics in a compact form. It is slightly dense because it enumerates return fields even though an output schema exists, but the additional notes about empty timestamps and is_dirty earn most of that space.

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?

For a no-parameter, read-only tool with an output schema and strong annotations, the description supplies all the remaining context an agent needs: deprecation, preferred alternative, related tool, prerequisite, and key behavioral semantics. Nothing material is missing.

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 no parameters, so the baseline is 4. The description correctly implies no input is required and does not invent parameter details.

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: reporting active document file details such as name, path, size, dates, type, configuration, and unsaved changes. It also explicitly distinguishes itself from get_model_info and get_custom_properties, so an agent can select it without opening sibling schemas.

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 says to use it to check what is open and whether there are unsaved changes before saving or closing, names the preferred replacement get_model_info, and names get_custom_properties for custom properties. It also states the prerequisite of an open active document.

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