Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_material

Assign a material by name to a SolidWorks part, making mass and density reflect real properties. Supports custom densities for materials not in the database.

Instructions

Assign a material by name (e.g. "6061 Alloy", "AISI 1020", "ABS").

Makes mass and density reflect a real material instead of the 1000 kg/m³ default. One SolidWorks does not have (say "TPU") comes with its density: density_kg_m3=1210 makes it, by that name, carrying only the density. Returns mass properties including density.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
databaseNo
density_kg_m3No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / density_kg_m3
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Density Kg M3"
+}
  2. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior: overriding the 1000 kg/m³ default and returning mass properties including density. However, it omits permission requirements, reversibility, and what happens if a material is already assigned, leaving real gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and useful, but the middle sentence ('One SolidWorks does not have (say "TPU") comes with its density: density_kg_m3=1210 makes it, by that name, carrying only the density') is garbled and hard to parse, undermining otherwise efficient content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers the core behavior and the custom-material fallback and states that mass properties are returned. It still leaves the 'database' parameter and permission/reversibility behavior undocumented, so it is only adequately complete.

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 0%, so the description must compensate. It adds real meaning for two params: 'name' (with material examples) and 'density_kg_m3' (with the example value 1210 for a custom material). The third parameter, 'database', is never mentioned anywhere, leaving a coverage hole.

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 clear verb+resource ('Assign a material by name') with concrete examples ('6061 Alloy', 'AISI 1020', 'ABS'), so an agent knows this sets a model's material. It does not explicitly contrast itself against siblings like get_mass_properties, but the resource is distinct enough to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage by explaining the effect (mass/density reflect a real material instead of the 1000 kg/m³ default) and the fallback for unknown materials via density_kg_m3. It never states when to call this versus alternatives or prerequisites (e.g., an open/active document), so guidance is implied rather than explicit.

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