Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Equations

list_equations
Read-onlyIdempotent

Lists the active part's or assembly's equations and global variables with solved values so you can see which dimensions they drive before changing or deleting them.

Instructions

List the active part's or assembly's equations and global variables, with their values.

Use it before set_equation or delete_equation, to see which values drive which dimensions. Needs: an open part or assembly. Read-only. Returns: equations, each with index, name, expression, kind (global_variable, dimension or other) and value (solved, in the document's units; null when SolidWorks has none), and count.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 'Read-only' is largely redundant. The description does add genuinely new behavior: the requirement for an open part or assembly and the meaning of a null value (SolidWorks has no solved value).

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, then clean 'Needs:' and 'Returns:' sections that are easy to scan. The only waste is restating 'Read-only' which the annotations already cover.

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-parameter read tool, the description covers the prerequisite state, the use case relative to sibling mutations, and the shape of the result, including the meaning of a null value. 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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a parameterless tool applies. The description correctly avoids inventing parameters and instead describes the returned fields.

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 active part's or assembly's equations and global variables, with their values'), including the scope of the active document. An agent can distinguish this from dimension-listing or mutation siblings 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?

Explicitly names the follow-on tools ('Use it before `set_equation` or `delete_equation`') and the reason (to see which values drive which dimensions), plus the prerequisite of an open part or assembly. The condition that selects this tool versus the mutation siblings is stated outright.

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