Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Reference Axis

create_axis

Adds a reference axis along the model's x, y, or z direction through the origin, creating the axis needed to rotate features with circular patterns.

Instructions

Add a reference axis along the model's x, y or z direction, through the origin.

Use it before pattern_circular, which rotates features about an axis. It is built where two default planes meet. Needs: an open part. Changes: adds an axis feature. Returns: axis with name (e.g. "Axis1", for create_reference_plane's axis), reference, planes and the feature counts.

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_axis"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe axis. `reference` ("x", "y" or "z") is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description goes further by disclosing the precondition (an open part must be open), the side effect category ('adds an axis feature'), and the concrete return payload including the generated name like 'Axis1'. It does not address what happens on repeated creation or naming collisions, which matters for a non-idempotent tool.

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 the action in the first sentence, then a when-to-use line, then compact 'Needs/Changes/Returns' labels. Every sentence carries information an agent needs; no filler.

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 single-parameter creation tool with nested input and an output schema, the definition covers purpose, sequencing, precondition, side effect, and return shape. Nothing essential for a correct call is missing, and the return summary is supplementary to the existing output schema.

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 100% and the schema already documents case-insensitivity and leading +/- stripping, so the description adds little that is new. It repeats the x/y/z direction set and adds the 'through the origin' constraint, which is placement context rather than parameter semantics; baseline 3 is appropriate.

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 ('Add a reference axis') plus the exact scope: along x, y or z, through the origin. It further differentiates itself from the related sibling by stating it is 'built where two default planes meet', which distinguishes it from create_reference_plane.

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?

It explicitly names a downstream consumer ('Use it before `pattern_circular`, which rotates features about an axis') and states a precondition ('Needs: an open part'). It stops short of naming when not to use it or what alternative to pick if an axis already exists, so it falls just below the top mark.

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