Skip to main content
Glama
solidworks-mcp

solidworks-mcp

create_plane

Creates a reference plane by offset, angle, or three points and returns its name so you can select it in SolidWorks.

Instructions

Creates a reference plane and returns its name, to use with select_plane. Three modes:

offset (default): parallel to 'reference' ("front", "top", "right" or a plane name) or to the planar face through face_point ([x, y, z] mm), offset_mm away; flip=True for the other side. angle: angle_deg > 0 turns the plane by that angle from 'reference' (or the face) about an axis lying in it or parallel to it: axis = "x", "y", "z" (model axes) or the name of a reference axis, or axis_edge_point = a point on a straight edge. flip reverses the angle. through_points: three vertices [[x, y, z], ...] of the part (corners), in mm. Using a model axis the first time adds a hidden reference axis to the tree.

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

Input Schema

NameRequiredDescriptionDefault
axisNo
flipNo
angle_degNoAngle in degrees (angle mode)
offset_mmNoOffset distance in mm (offset mode)
referenceNofront
face_pointNo
through_pointsNo
axis_edge_pointNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.1
    • addedInput schema / properties / angle_deg
      Added value: +{
      +  "default": 0,
      +  "description": "Angle in degrees (angle mode)",
      +  "exclusiveMaximum": 360,
      +  "minimum": 0,
      +  "title": "Angle Deg",
      +  "type": "number"
      +}
    • addedInput schema / properties / axis
      Added value: +{
      +  "default": "",
      +  "title": "Axis",
      +  "type": "string"
      +}
    • addedInput schema / properties / axis_edge_point
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "number"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Axis Edge Point"
      +}
    • addedInput schema / properties / offset_mm / default
      Added value: +0
    • changedInput schema / properties / offset_mm / description
      Previous value: -"Offset distance in mm"New value: +"Offset distance in mm (offset mode)"
    • removedInput schema / properties / offset_mm / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / offset_mm / minimum
      Added value: +0
    • addedInput schema / properties / through_points
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "items": {
      +          "type": "number"
      +        },
      +        "type": "array"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Through Points"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "offset_mm"
      -]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the bar is lower. The description still adds non-obvious traits: it returns a name meant to be chained into select_plane, and using a model axis the first time silently adds a hidden reference axis to the model tree. It doesn't describe failure modes for invalid points or duplicate planes, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and return value, then a compact mode list where each mode's required parameters sit on their own line. Every sentence carries information, including the hidden-axis note, which is not stated elsewhere.

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 an 8-parameter mode-driven geometry constructor with an output schema present, the description covers each mode's parameter combination and the tree side effect. Error handling and the exact contents of the returned value are left to the output schema and runtime, which is acceptable.

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 only 25%, with axis, flip, reference, face_point, through_points and axis_edge_point all undocumented in the schema, so the description must compensate and largely does: it defines reference values ("front", "top", "right", or a plane name), the mode-dependent meaning of flip, axis as model axes or a reference axis name, and axis_edge_point as a point on a straight edge. It stops short of specifying valid axis-name domains and states units only for points, not offsets or angles.

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+resource (creates a reference plane) and its return value (the plane's name, for use with select_plane), then enumerates three distinct modes. An agent can distinguish this from create_axis or any other sibling purely from the description.

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?

Each mode's selection criteria are spelled out: offset needs 'reference' or face_point plus offset_mm, angle requires angle_deg>0 and an axis specification, through_points requires three vertex coordinates. There is no explicit 'do not use for X' or named alternative beyond select_plane, but the mode routing is clear enough to act on.

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