Skip to main content
Glama
Sign In
CAD-CAE-Agent SolidWorks MCP Server

CAD-CAE-Agent SolidWorks MCP Server

by caoguanqiu1-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_spline

Insert a free-form spline curve into the active SolidWorks sketch by defining control points, ideal for organic shapes and smooth transitions.

Instructions

Add a spline curve to the current sketch.

Creates a smooth, free-form spline curve that passes through or near the specified control points. Splines are ideal for creating organic shapes, complex profiles, and smooth transitions in industrial design.

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 input data value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the spline 'passes through or near' control points but does not state prerequisites (e.g., active sketch), side effects (e.g., sketch modification), or whether the operation is destructive. This is insufficient transparency.

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?

The description is two sentences: a clear first sentence stating the action, and a second sentence providing use-case context. No redundant or irrelevant information.

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?

Given the tool's complexity (nested objects, one parameter) and the presence of an output schema, the description covers purpose and usage adequately. It implicitly requires a current sketch but does not explicitly state prerequisites. Overall, reasonable completeness.

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 coverage is 100% with a description for the 'points' parameter. The tool's description adds that the spline 'passes through or near' the points, which provides additional behavioral meaning beyond the schema's 'List of spline control points with x, y coordinates.' Baseline 3 is appropriate with minor improvement.

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 clearly states 'Add a spline curve to the current sketch' with a specific verb and resource. It distinguishes splines from other sketch tools (e.g., add_line, add_circle) by highlighting free-form curves for organic shapes, which is unique among siblings.

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?

The description provides clear context by stating splines are 'ideal for creating organic shapes, complex profiles, and smooth transitions.' However, it lacks explicit when-not-to-use guidance or direct comparison with alternative tools like add_line or add_arc.

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