Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Sketch Linear Pattern

sketch_linear_pattern

Repeats sketch entities in a straight line at fixed spacing to build rows of holes or slots before one cut; requires an open sketch and returns the new pattern.

Instructions

Repeat sketch entities in a straight line at a fixed spacing.

Use it for rows of holes or slots before one cut. Needs: an open sketch (create_sketch). Changes: adds copies of the entities. Returns: pattern with id, entities, count, spacing and direction.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesA mapping: `entities` (ids to repeat), `direction_x`/ `direction_y` (default 1, 0), `spacing` (mm, default 10) and `count` (instances, default 3).

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, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description adds what structured data does not: it requires an open sketch as a precondition and discloses that the operation adds copies of existing entities rather than replacing them. It does not note that re-running duplicates entities (dropping idempotentHint to false), a small remaining gap.

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 labeled Needs/Changes/Returns lines that are easy to scan. The Returns clause restates fields the output schema already defines, which is wasted space, though only one short clause.

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?

With an output schema present, the description needn't enumerate return values, so the only real requirement is stating the sketch precondition and the mutation effect, both of which it does. For a single-parameter, non-destructive pattern operation this is close to sufficient; nothing about counts or entity validity limits is mentioned, but the schema handles defaults.

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 input_data already documents entities, direction_x/y defaults, spacing and count. The description adds no parameter-level meaning beyond that, 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?

"Repeat sketch entities in a straight line at a fixed spacing" gives a specific verb (repeat) and resource (sketch entities) plus the discriminating geometry (linear vs. the sibling circular pattern). It does not name the alternative outright, but the "straight line" framing separates it from sketch_circular_pattern without opening either schema.

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?

"Use it for rows of holes or slots before one cut" supplies a concrete usage context, and "Needs: an open sketch" states the prerequisite state and names the sibling that produces it. No explicit exclusion or named alternative is given, which keeps it below 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