Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get File Properties

get_file_properties
Read-onlyIdempotent

Retrieve the active document's file details—name, path, size, dates, type, configuration, and unsaved-changes status—to verify what is open before saving or closing.

Instructions

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 observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description earns credit for the operational prerequisite of requiring an active document and for the non-obvious edge case that date fields are empty for a never-saved document. It restates "Read-only" redundantly with the annotations and spends most of its remaining budget on return fields already declared in the output schema.

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?

Front-loaded with the resource and scope, then use case, alternatives, prerequisite and returns in a predictable order. The trailing "Returns:" block largely duplicates the existing output schema, which costs some tightness, but the sentences are short and each carries actionable content.

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 zero-parameter read tool with rich annotations and a declared output schema, everything an agent needs is present: prerequisite, read-only nature, sibling routing, and the one return nuance not captured by the schema. No gap remains that would cause a misinvocation.

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 for the description to disambiguate and the baseline of 4 applies. It correctly signals that no arguments are required by framing the call as a report on the currently active document.

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 ("Report") and resource ("the active document's file details") and enumerates exactly what is returned: name, path, size, dates, type, configuration and unsaved changes. It explicitly distinguishes itself from `get_model_info` (model/rebuild status) and `get_custom_properties` (custom properties), so an agent can separate the three property tools without opening a schema.

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?

Gives a concrete use case ("check what is open and whether it has unsaved changes before saving or closing") plus a prerequisite ("Needs: an open, active document") and routes the two nearest alternatives to their own tools with the condition that selects them. Nothing about when to pick this over a sibling is left to inference.

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