Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Get Custom Properties

get_custom_properties
Read-onlyIdempotent

Reads the active SolidWorks document's custom properties, including PartNo, Description, Revision, and resolved $PRP links, with optional configuration-specific values for title blocks and BOMs.

Instructions

Read the active document's custom properties, such as PartNo, Description or Revision.

File-level properties (the default) are what drawing title blocks and BOMs usually read; give configuration for that configuration's own. Needs: an open, active document. Read-only. Returns: data with properties, each name mapped to its value and resolved value (a $PRP link evaluated).

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

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: `configuration` reads that configuration's properties instead of the file's.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior, so the description does not need to re-explain safety. It adds useful operational context beyond annotations: the open active document requirement, the default file-level scope, and what the resolved value means for $PRP links. It does not discuss permission failures or rate limits, but those are less critical here.

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

Conciseness5/5

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

The description is front-loaded with the core action and examples, then moves efficiently through scope, prerequisite, safety, and return shape. Every sentence carries useful information, and there is no redundant restatement of annotations or 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?

For a read-only, single-parameter tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what it reads, the default scope, how to request configuration-specific properties, the active-document prerequisite, and a brief return shape including resolved values. No critical context appears to be 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 configuration parameter is already fully documented in the input schema, so the baseline would be 3. The description adds practical meaning by explaining that file-level is the default and what title blocks and BOMs usually read, and that providing configuration switches to that configuration's own properties.

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?

The description gives a specific verb and resource: read the active document's custom properties, with concrete examples such as PartNo, Description, and Revision. It also distinguishes the two scopes it can read, file-level versus configuration-specific, so an agent can tell what result it will get 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 Guidelines4/5

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

The description clearly states the default behavior and the alternative: omit configuration for file-level properties that drawing title blocks and BOMs usually read, or provide configuration for that configuration's own properties. It also states the prerequisite of an open, active document. It does not explicitly name sibling tools or exclusions, so it falls short of fully explicit routing guidance.

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