Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Available Materials

list_available_materials
Read-onlyIdempotent

Lists materials in installed SolidWorks libraries so you can find the exact name set_material requires; filter by name or classification with search.

Instructions

List the materials in the installed SolidWorks material libraries.

Use it to find the exact name set_material needs; filter with search (e.g. "steel" or "6061"). It reads every .sldmat library SolidWorks is set to use. Needs: SolidWorks installed. Read-only. Returns: data, each material's name, classification and database; the message gives the total and the folders read, so an empty search can be told from a missing library.

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

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: `search` filters by name or classification, not case-sensitive.

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 readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds non-obvious context: the environment dependency ("Needs: SolidWorks installed"), the scope ("reads every .sldmat library SolidWorks is set to use"), and the fact that the message reports totals and folders read so an empty result can be distinguished from a missing library. It stops short of noting cost or latency of scanning all libraries, which keeps it from 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?

Front-loaded with the purpose in sentence one, then scenario, then prerequisites, then return shape—a sensible order with no padding. The "Returns:" sentence slightly overlaps an existing output schema, though its point about distinguishing an empty search from a missing library does earn its place.

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 lookup tool with an output schema, this covers everything an agent needs: what is listed, how to filter, the environment prerequisite, the read-only nature, and how to interpret an empty result versus an unconfigured library. Nothing material 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 the single optional `search` parameter is fully documented there, including the same examples ("steel", "6061") the description repeats. The description adds the useful note that the filter matches classification as well as name, but this largely tracks the schema's own wording, 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—"List the materials in the installed SolidWorks material libraries"—and immediately ties it to the downstream consumer, `set_material`. That distinguishes it from the sibling `set_material` and from other `list_*` tools that enumerate documents, features, or dimensions.

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 the concrete driving scenario ("find the exact name `set_material` needs") and names the sibling it feeds, so the agent knows when this tool is a prerequisite rather than a substitute. It also tells the agent how to narrow results with `search`, so no exclusions are left to inference for a read-only lookup tool.

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