Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Rebuild Model

rebuild_model
Idempotent

Rebuild the active SolidWorks part or assembly after edits to confirm model health and report any failing features with causes and fixes.

Instructions

Rebuild the active model and report each feature that fails, with the reason and a fix.

Use it after set_dimension or other edits to confirm the model is sound. Failing features make the call an error whose data.errors names each one, its SolidWorks error, what it depends on and a hint; warnings alone still succeed. Needs: an open part or assembly. Changes: rebuilds the model. Returns: data with rebuilt, errors, error_count, warning_count and summary.

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

Input Schema

NameRequiredDescriptionDefault
input_dataNoNothing is required: `top_level_only` is off (a full rebuild).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the failure contract (failing features turn the call into an error), the shape of the error payload (data.errors naming each feature, its SolidWorks error, its dependencies, and a hint), and the important nuance that warnings alone still succeed. It also states the required document state (open part or assembly), which annotations do not cover.

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-loads the core action and failure contract, then closes with a compact Needs/Changes/Returns block that is easy to scan. The Returns enumeration mildly restates what the output schema already provides, a small redundancy in an otherwise tight definition.

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?

Covers the prerequisite document state, what the call mutates, the success/failure distinction, and the error payload contents—everything needed to invoke it and interpret the outcome. With annotations and an output schema also present, no meaningful gap remains for a rebuild tool.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already explains top_level_only and its default full-rebuild behavior. The description adds nothing about the parameter itself, which is acceptable given full schema coverage but is the baseline rather than added value.

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?

Specific verb (rebuild) plus the exact resource (the active model), with the added promise of per-feature failure reporting including reason and fix. The second line anchors it to a concrete workflow point ('after set_dimension or other edits'), which separates it from passive inspection siblings like get_model_info.

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 a clear when-to-use trigger ('after set_dimension or other edits to confirm the model is sound') and a prerequisite (an open part or assembly). It does not explicitly name or exclude the adjacent validation sibling verify_model, so the agent must infer that boundary.

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