Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Calculate Mass Properties

calculate_mass_properties
Read-onlyIdempotent

Measure the active part or assembly's mass properties—volume, mass, center of mass, and inertia—using this deprecated alias for get_mass_properties.

Instructions

Deprecated: use get_mass_properties.

Measure the active part or assembly's mass properties (the old name of get_mass_properties).

It returns exactly what get_mass_properties returns; use that instead. 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²) and principal_axes.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesNothing: it always measures the active model.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, but the description adds real context beyond them: the 'it rebuilds first' side effect and the prerequisite of an open document. The enumerated return fields largely restate the existing output schema, so it stops short of a 5.

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 correctly front-loaded and the sentence count is low. However, the trailing list of return fields duplicates the output schema and occupies roughly a third of the text without adding call-relevant information.

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 deprecated one-parameter alias with annotations and an output schema, the description covers migration path, prerequisite, read-only nature, rebuild behavior, and return shape. An agent has everything needed to decide not to call it or to call it correctly.

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 coverage is 100% and the single parameter is an empty object that the schema itself labels 'Nothing: it always measures the active model.' The description's mention of the active model matches rather than extends that, so baseline 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 specific verb and resource ('Measure the active part or assembly's mass properties') and immediately frames the tool as the deprecated alias of get_mass_properties, so an agent can distinguish it from the sibling 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 an explicit when-not ('Deprecated: use get_mass_properties') and names the alternative twice, plus the precondition of an open part or assembly. Nothing about tool selection 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