Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_plate

Creates a centered rectangular plate in SOLIDWORKS from width, length, and thickness values, rebuilding the model and clearing existing holes.

Instructions

建一块长方形平板(原点居中,厚度沿 +Z 拉伸)。会重建模型并清空已有孔。

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

Input Schema

NameRequiredDescriptionDefault
width_mmNo
length_mmNo
thickness_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden, and it does disclose one critical trait: the operation rebuilds the model and destroys existing holes. It omits other important behavior such as whether an open document/part is required, whether prior non-hole features survive, and whether the call is undoable.

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?

Two compact sentences, purpose first and the destructive side effect second, with no filler. The second sentence is terse enough that its scope (which holes, in which document) is left ambiguous, but nothing is redundant.

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 three-parameter creation tool with no annotations and no output schema, the definition covers what is built, its orientation, and the main destructive side effect. Preconditions (active document/part) and the return behavior remain unstated, which is a real but modest gap.

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 0%, so the description must compensate; it clarifies the geometric frame (centered origin, +Z extrusion) which the schema does not convey. It still does not explain the width vs. length distinction or confirm millimetre units beyond what the parameter titles already imply.

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 — builds a rectangular plate — plus geometric scope (origin centered, thickness extruded along +Z). This clearly separates it from siblings like sw_hole and sw_holes_clear, which modify an existing body rather than create the base plate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied: this is the base-geometry creation step, and the note that it rebuilds the model and clears existing holes hints at ordering constraints. However, it never states when to prefer this over alternatives or that hole features must be re-added afterward via sw_hole.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.