Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Sketch Spline

add_spline

Draws a spline in millimeters through point coordinates in an open sketch, enabling free-form curves such as aerofoil or handle profiles.

Instructions

Draw a smooth spline through a list of points in the open sketch, in mm.

Use it for free-form curves such as an aerofoil or a handle profile. Needs: an open sketch (create_sketch). Changes: adds a spline. Returns: spline with id, control_points and point_count.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe spline. `points` (a list of {"x", "y"} in mm) is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"The input data value."New value: +"The spline. `points` (a list of {\"x\", \"y\"} in mm) is\nrequired."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover the read/write and idempotency profile; the description adds the precondition (open sketch required), the effect ('adds a spline'), and the shape of what comes back. It does not mention a minimum point count, whether the curve is closed, or ordering of points.

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?

Three tight sentences with a deliberate Needs/Changes/Returns pattern; the purpose is front-loaded and no sentence is redundant.

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?

Covers purpose, precondition and effect for a simple one-parameter geometry tool, and an output schema exists so return details are already structured. Minor gaps around point ordering and minimum point count keep it from being fully complete.

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 `points` field already documents x/y in mm, so the description's 'in mm' and point list add little beyond the schema. Baseline 3 is appropriate when the schema carries the parameter meaning.

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 ('Draw a smooth spline through a list of points in the open sketch, in mm') and adds the domain examples 'aerofoil or a handle profile', which implicitly separates it from the straight-line/arc siblings like add_line and add_arc.

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 clear positive selection rule ('free-form curves') and a hard prerequisite ('Needs: an open sketch (`create_sketch`)'). It does not state when not to use it or what happens if the sketch is closed, so it stops short of full alternative routing.

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