Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Set Material

set_material
Idempotent

Assign an exact library material to the active part, updating its mass and drawing title-block Material field; confirm the name with available materials before applying.

Instructions

Assign a library material to the active part, e.g. "AISI 1020" or "6061-T6 (SS)".

The material sets the mass and what a title block's Material field shows. The name must match the library exactly; find it with list_available_materials. The material is read back, so success means it applied. Needs: an open, active part. Changes: the part's material. Returns: data with material, database and configuration.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe material. `material_name` is required; `database` ("SOLIDWORKS Materials") and `configuration` (all) have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by naming the prerequisite (open, active part), the exact effect ("the part's material", which drives mass and the title block Material field), the strict matching constraint, and the verification semantics ("The material is read back, so success means it applied"). With idempotentHint=true already declaring repeat-safety, this is a strong complement rather than a restatement.

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 the action and an example, then prerequisites, effect and return shape in short labeled clauses ("Needs:", "Changes:", "Returns:"). Minor redundancy repeating a default already documented in the schema.

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?

Covers prerequisites, mutation target, failure mode (exact name match) and success verification; return values are also backed by an output schema, so nothing an agent needs to invoke this 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?

Schema coverage is 100% and each nested property already carries a description including defaults for database and configuration, so the description only repeats the example material names and the pointer to list_available_materials. Baseline 3 applies since the schema carries the parameter burden.

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 ("Assign a library material to the active part") and gives concrete example values, making it immediately distinguishable from sibling readers like get_material and list_available_materials.

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 precondition ("Needs: an open, active part") and routes the agent to list_available_materials to resolve the exact library name. It lacks an explicit statement of when not to use it versus read-only siblings, but the context is unambiguous.

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