Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Manage File Properties

manage_file_properties
Destructive

Read or update file-level properties of SolidWorks files on disk, including property values and optional system properties.

Instructions

Read or change the file-level properties of a SolidWorks file on disk.

Not available yet: no adapter implements it, so every call returns an error with error_type: "not_supported". It is planned for a future release. To read or set custom properties on the active model today, use get_custom_properties and set_custom_property. Changes: once available, the file's properties. Returns: once available, the properties under data.

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": "manage_file_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe operation. `operation` is required; `file_path` or `source_path`, `properties` and `include_system` have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"The input data value."New value: +"The operation. `operation` is required; `file_path` or\n`source_path`, `properties` and `include_system` have defaults."
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Goes well beyond the annotations by disclosing unavailability, the exact error type returned, and future plans — a genuine behavioral fact an agent cannot infer from readOnlyHint=false / destructiveHint=true. However, the description never addresses the destructive surface the annotations advertise (delete/overwrite of on-disk files per the schema's copy/move/delete/rename), so the safety profile is left partly unexplained.

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-loads the most decision-relevant fact (unavailable, use alternatives) in the second sentence, before any detail. The trailing "Changes: once available... Returns: once available..." sentences are largely redundant given the output schema exists, which keeps it from a 5.

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 tool that always errors, the description gives the agent everything needed to make the right call: it is unavailable, what error to expect, and where to go instead. The only gap is the unresolved tension between the property-focused description and the file-operation schema, which leaves the tool's eventual contract unclear.

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?

Schema description coverage is 100%, so the baseline is 3; the description adds no parameter-level meaning at all. Worse, it arguably conflicts with the schema, which exposes `operation` values copy/move/delete/rename and `source_path`/`target_path`, none of which the description's "file-level properties" framing explains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair and resource: "Read or change the file-level properties of a SolidWorks file on disk," and immediately distinguishes itself from get_custom_properties / set_custom_property, which target the active model. The purpose is somewhat muddied by the schema, whose `operation` parameter is documented as copy/move/delete/rename — file operations rather than property reads/writes — so the agent gets two different pictures of what this tool does.

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 when NOT to use it: "Not available yet: no adapter implements it, so every call returns an error with `error_type: not_supported`," and names the concrete alternatives to use instead (get_custom_properties and set_custom_property). This is exactly the when/when-not/alternative guidance the dimension rewards.

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