Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Delete Equation

delete_equation
Destructive

Removes an equation or global variable from the active part or assembly by name. Use it to clear obsolete equations, then check list_equations to confirm what remains.

Instructions

Delete an equation or global variable of the active part or assembly, by name.

A dimension the equation drove keeps its last value; an equation that used a deleted global variable stops solving, so check list_equations afterwards. Needs: an open part or assembly with that equation. Changes: removes the equation. Returns: deleted and the equations left (names).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`name`, as `list_equations` gives it.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already flag this as destructive and non-idempotent, but the description goes further by explaining the consequences: a dimension driven by the equation keeps its last value, and other equations referencing a deleted global variable stop solving. It also names the returned fields. That is real behavioral context beyond what the annotations provide.

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 short and front-loaded: the opening sentence names the action and resource, then follow the caveats and the Needs/Changes/Returns lines. Not one sentence is wasted.

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 single-parameter mutation with annotations and an output schema, the description covers prerequisites, side effects on dependent equations and dimensions, and the verification step. No gap is left that would stop an agent from calling it correctly.

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 schema already says the name must match what list_equations returns and gives an example ('Width'). The description's 'by name' doesn't add anything the schema doesn't already state, so it stays at the baseline 3.

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 (delete) and resource (equation or global variable), plus the scope: the active part or assembly, by name. That's enough for an agent to tell it apart from set_equation or list_equations without reading any 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?

Gives the precondition (an open part or assembly that contains the equation) and tells the agent to check list_equations afterwards. It doesn't explicitly say when not to use it, e.g. to rename or modify an equation use set_equation, so it falls short of a 5.

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