Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Get Material

get_material
Read-onlyIdempotent

Read the active part's material or a library material and return its density, elastic modulus, yield strength, and other properties for sizing or comparison before assignment.

Instructions

Report the active part's material with its strength and stiffness, or any library material's.

Use it to size a part (the elastic modulus and yield strength) or to compare materials before set_material, and before get_mass_properties (without a material SolidWorks uses a default density). Give material to read a library material without assigning it: no document is needed and none changes. Needs: an open, active part unless material is given (any other document is wrong_document_type). Read-only. Returns: data with material (null when none is assigned), database, density_kg_m3, source (part or library) and properties: elastic_modulus, poissons_ratio, shear_modulus, tensile_strength, yield_strength, compressive_strength, density, thermal_expansion, thermal_conductivity, specific_heat, each with value in SI units (Pa; divide by 1e6 for MPa), unit and label. A property the library doesn't hold for that material is left out.

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

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: `configuration` defaults to the active one; `material` (and `database`) read a library material instead.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations (readOnly/idempotent/non-destructive) by naming the precondition — an open, active part unless `material` is given — and the exact failure mode (`wrong_document_type`). It also discloses that a library read mutates nothing and that missing library properties are simply omitted rather than errored.

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 purpose, then usage, then preconditions, then returns — a sensible order with no filler sentences. The long enumeration of return properties is somewhat redundant given an 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool this is complete: preconditions, error case, mutation guarantees, SI unit convention (Pa, divide by 1e6 for MPa), and the null-material case are all covered. Nothing an agent needs in order 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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the side-effect semantics of `material` (reads without assigning, no document required) and the precedence role of `database` ("look in first"), which the schema alone states more flatly.

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 — "Report the active part's material with its strength and stiffness, or any library material's" — and distinguishes the two retrieval modes (active part vs. library lookup) up front. An agent can tell this apart from siblings like set_material or get_mass_properties without opening the 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?

Explicit when-to-use guidance: sizing a part, comparing materials before `set_material`, and running before `get_mass_properties` (with the reason: default density without a material). It also states the alternative mental model — pass `material` to read a library entry without assigning it, no document needed, nothing changes.

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