Skip to main content
Glama
NejcDvorsek

SolidWorks MCP

by NejcDvorsek

add_plane

Creates reference planes for sketches by offsetting or rotating a base plane, or defining a plane through a point and normal vector.

Instructions

Make a reference plane to sketch on: an offset or a turned plane, its position a dimension.

base moved offset_mm along its normal (base: front/top/right or a plane by name), or a default plane turned angle_deg about a model axis it holds, about='x'/'y'/'z' (front holds x and y, top x and z, right y and z), by the right-hand rule. For both, turn first, then offset that plane. Or the plane through model point through=[x, y, z] square to normal=[dx, dy, dz] (any direction, e.g. square to a cone's generatrix). Returns its name for plane= arguments, and origin_mm, normal, x_axis and y_axis: a point (u, v) on it is origin + u x_axis + v y_axis.

Input Schema

NameRequiredDescriptionDefault
baseNofront
nameNo
aboutNo
normalNo
throughNo
angle_degNo
offset_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.3

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses operation order ('turn first, then offset'), return values, and the plane coordinate frame. It does not cover failure conditions or default behavior when parameters are omitted, which keeps it from a 5.

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?

The description is front-loaded with purpose and then proceeds through construction modes efficiently. It is dense and somewhat run-on, but nearly every clause contributes geometric meaning, so it remains useful rather than padded.

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 7-parameter geometry tool with no annotations and no output schema, the description provides substantial completeness: construction modes, axis conventions, and return coordinate frame. It still omits the name parameter's purpose and any error/omission behavior.

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?

Schema description coverage is 0%, so the description must compensate. It explains base, offset_mm, angle_deg, about axis mappings, through, and normal semantics in useful detail, but the name parameter is left unexplained and defaults are only partially implied.

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 opens with a specific verb and resource: 'Make a reference plane to sketch on.' It immediately clarifies the tool's role in creating construction geometry, which distinguishes it from sketch/profile creation siblings like add_sketch.

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?

The description explains the available construction modes in detail, but it does not explicitly say when to choose this tool over siblings such as add_axis or add_sketch, nor does it state exclusions. Usage is implied by the mode descriptions rather than routed against alternatives.

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