Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Reference Plane

create_reference_plane

Creates a reference plane offset from, angled to, or placed on a face or plane, so you can sketch beyond SolidWorks' three default planes.

Instructions

Add a reference plane offset from, at an angle to, or on a plane or flat face.

Use it to sketch somewhere other than the three default planes: pass the new plane's name to create_sketch. Offset: reference and a non-zero offset (mm). Angle: reference, angle (degrees) and axis, an axis lying in the reference (make one with create_axis). Face: face_point, a point on a flat face (sloped or not), with an offset or 0 for a plane on the face. Needs: an open part. Changes: adds a plane feature. Returns: plane with name and the inputs used.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe plane. Exactly one of `reference` and `face_point`; then `offset`, or `angle` with `axis`; `flip` is off.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: a precondition ('Needs: an open part'), the effect ('Changes: adds a plane feature'), and the return payload. What it does not cover is failure behavior, e.g. what happens with a duplicate plane name or an invalid face_point, which matters for a non-idempotent mutation.

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-loaded purpose followed by a compact decision tree over the three modes, then terse Needs/Changes/Returns lines. Dense but every clause carries information; the fragment style ('Angle: `reference`, `angle` (degrees) and `axis`...') is slightly telegraphic but still parseable.

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 tool with a nested input object and an output schema, the definition covers preconditions, the exact parameter combinations per mode, the mutation effect, and how the result feeds a sibling tool. An agent has everything needed to attempt a correct call.

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?

With 100% schema description coverage, the schema already documents every field including units and the 'exactly one of reference and face_point' rule. The description restates those rules in per-mode recipes (offset mm, angle degrees with axis, face_point with offset 0) but adds little syntax the schema does not already carry, so baseline 3 applies.

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 and resource ('Add a reference plane') and immediately enumerates the three construction modes: offset from a plane, at an angle to a plane, or on a flat face. This is clearly distinguishable from siblings like create_axis and create_reference_point.

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

Usage Guidelines5/5

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

Gives an explicit motivation ('Use it to sketch somewhere other than the three default planes'), the downstream wiring ('pass the new plane's name to create_sketch'), and per-mode input recipes including a pointer to create_axis when an angle is needed. When-to-use and the relevant alternative are both stated.

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