Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Get Mass Properties

get_mass_properties
Read-onlyIdempotent

Measure the active part or assembly's volume, surface area, mass, center of mass, and moments of inertia to check weight or balance.

Instructions

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

Use it to check weight or balance. 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. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing a real side effect ('It rebuilds first') and a precondition ('Needs: an open part or assembly'), neither of which is encoded in readOnlyHint/idempotentHint. It also explains that the result is material-dependent, which prevents misuse. The rebuild disclosure is the most valuable piece of context here, though the cost/consequence of that rebuild is not spelled out.

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 measurement, then uses compact 'Needs:' and 'Returns:' segments that scan well. The full Returns enumeration with units partly duplicates what the output schema already provides, making it slightly longer than strictly necessary.

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?

Given a tool with one empty parameter, full annotations, and an output schema, the description supplies everything else an agent needs: precondition, side effect, material dependency, alternative destination, and unit conventions. Nothing required to call it correctly 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 single parameter is fully documented in the schema as an empty, optional object, and the description reinforces that the tool 'always measures the active model' rather than accepting inputs. With 100% schema coverage and only one pass-through parameter, there is little meaning left to add.

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 enumerates exactly which quantities are computed (volume, surface area, mass, centre of mass, moments of inertia). The scope qualifier 'active' immediately distinguishes it from a pass-a-model-in tool.

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 weight or balance') plus an explicit routing rule away to 'verify_model' when the goal is comparison against expected values. It also flags the prerequisite dependency on 'set_material', so the agent knows where mass values actually come from.

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