Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Mass Properties

get_mass_properties
Read-onlyIdempotent

Measures the active part or assembly's mass properties—volume, surface area, mass, center of mass, and moments of inertia—for CAD model analysis and validation.

Instructions

Measure the active part or assembly's mass properties: volume, surface area, mass, centre of mass and moments of inertia.

The same as calculate_mass_properties, which it calls. To compare a model with the values you expect, use verify_model. Mass depends on the assigned material (set_material). Needs: an open part or assembly. Read-only. It rebuilds first. Returns: mass_properties with volume (mm³), surface_area (mm²), mass (kg), center_of_mass (mm), moments_of_inertia (kg·mm², about the centre of mass) and principal_axes.

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

Input Schema

NameRequiredDescriptionDefault
input_dataNoOptional, and empty: it always measures the active model.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / input_data / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "description": "Input schema for mass properties analysis.\n\nAttributes:\n    include_hidden (bool): The include hidden value.\n    model_path (str | None): The model path value.\n    reference_coordinate_system (str | None): The reference coordinate system value.\n    units (str): The units value.",
-    "properties": {
-      "include_hidden": {
-        "default": false,
-        "description": "Include hidden components",
-        "type": "boolean"
-      },
-      "model_path": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Path to the model file"
-      },
-      "reference_coordinate_system": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Reference coordinate system alias"
-      },
-      "units": {
-        "default": "metric",
-        "description": "Units for mass properties",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "description": "Input schema for mass properties analysis.\n\nIt has no fields: the tool always measures the active model. Inputs it\nused to take are refused (``input_compat.REMOVED_INPUTS``).",
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / input_data / description
      Previous value: -"The input data value.\n                                                      Defaults to None."New value: +"Optional, and empty: it always measures the active model."
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavior beyond them: it rebuilds the model before measuring, it requires an open document, and it sets out exactly what each returned quantity means and in which units. The rebuild disclosure is the kind of side effect an agent cannot infer from structured fields.

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 what is measured, then prerequisites, then returns; each paragraph is short and scannable. The return-value paragraph is somewhat redundant given a dedicated output schema exists, though the units it supplies remain useful.

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-argument measurement tool, the definition covers purpose, prerequisites, material dependency, side effect (rebuild), and the shape and units of the result. Nothing an agent needs to invoke it correctly is missing.

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?

The single parameter is fully documented in the schema (100% coverage) as optional, nullable, and functionally empty since the tool always measures the active model. The description adds only the implicit 'active part or assembly' framing, which the schema already covers, so the baseline of 3 applies.

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 concrete verb (measure) and names the exact quantities produced: volume, surface area, mass, centre of mass, moments of inertia. It also places itself relative to siblings by declaring it is the same operation as `calculate_mass_properties`, which it calls, and by pointing at `verify_model` for a different job.

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?

Gives a clear use context (compare against expected values -> use `verify_model` instead), a prerequisite (an open part or assembly), and a dependency (mass comes from the material set by `set_material`). The only gap is that it never says why an agent would pick this over `calculate_mass_properties`, presumably because they are identical.

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