Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Reference Point

create_reference_point

Add a reference point along an edge by distance or percentage, or at a face center, to mark positions for later features or measurements.

Instructions

Add a reference point on an edge (at a distance or percentage along it) or at the centre of a face.

Use it to mark a position for a later feature or measurement. Pick the edge or face with a point on it in mm. Needs: an open part with that edge or face. Changes: adds a point feature. Returns: point with mode, at_mm, distance_mm or percent, 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_reference_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe point. `mode` (along_curve or face_center) and `x`, `y`, `z` (mm) are required; for along_curve give one of `distance` (mm) or `percent`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the description's job is to add detail, and it does: it says what changes ('adds a point feature') and what comes back ('point' with mode, at_mm, distance_mm or percent, plus feature counts). It does not warn that repeated calls accumulate points (non-idempotent), which would have earned 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?

Front-loaded with the core action, then structured with explicit 'Needs:', 'Changes:' and 'Returns:' labels, so the scanning agent finds prerequisites and effects quickly. Slightly more verbose than necessary, since the returns sentence duplicates the output schema.

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 single nested-parameter mutation tool with an output schema, the definition covers purpose, prerequisites, mutation effect and result shape. The main omission is the non-idempotent consequence of repeated calls, which the annotations only imply.

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 nested object already documents x/y/z in mm, the two mode values, and the 'exactly one of distance or percent' rule. The description restates the same constraints rather than adding new meaning such as default units behaviour or how percentage is rounded, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Add a reference point') and pins down the two geometric cases: a point on an edge at a distance/percentage, or the centre of a face. That is enough to tell it apart from a reference plane or axis tool, though no sibling is named explicitly.

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?

Gives a use case ('mark a position for a later feature or measurement') and a concrete prerequisite ('an open part with that edge or face', with a point on the target in mm). It does not state when not to use it or name an alternative tool, so it falls short of a 5.

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