Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

delete_equation

Delete a SOLIDWORKS equation or global variable by name or index, then rebuild the model. Deletion is refused when other equations depend on that variable.

Instructions

Delete an equation or global variable by name or index (see list_equations) and rebuild. A global variable that other equations use is refused.

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

Input Schema

NameRequiredDescriptionDefault
nameNoGlobal variable or dimension name on the left of the equation
indexNoIndex from list_equations (instead of name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the rebuild side effect and the refusal case for a referenced global variable, but omits permissions, reversibility, behavior when the name is not found, and whether both name and index may be supplied.

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?

Two tightly written sentences with the operation and identifier forms front-loaded, followed by the important refusal condition. No wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter deletion tool with no output schema and fully described parameters, the description covers the key action, identifier sources, rebuild behavior, and one important refusal case. The main remaining gap is failure behavior for nonexistent targets, which is minor.

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 description coverage is 100%, so the schema already documents both parameters including that index comes from list_equations. The description's 'see list_equations' is redundant and adds no precedence rule when both name and index are provided, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Delete an equation or global variable') and mentions both supported identifier forms. It references list_equations for index lookup, making the intended scope clear without naming a sibling it is not.

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?

It tells the agent how to obtain an index ('see list_equations') and provides a usage constraint: deleting a global variable referenced by other equations is refused. It lacks explicit when-not-to-use guidance against set_equation or other delete tools, but the context is clear.

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