Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sketch_linear_pattern

Repeat sketch entities in a row or grid by setting counts, spacing, and angles to create patterns like rows of holes before a cut.

Instructions

Repeats sketch entities of the open sketch in a row or a grid (e.g. a row of holes before one cut). entity_points: [[x, y], ...] one point on each entity. count_x copies spacing_x_mm apart along the direction at angle_x_deg from sketch X; count_y / spacing_y_mm / angle_y_deg add a second direction. Replaces the selection.

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": {
      "entity_points": "<entity_points>",
      "count_x": "<count_x>",
      "spacing_x_mm": "<spacing_x_mm>"
    },
    "name": "sketch_linear_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
count_xYesInstances along the first direction, original included
count_yNoInstances along the second direction, original included
angle_x_degNo
angle_y_degNo
spacing_x_mmYesSpacing along the first direction in mm
spacing_y_mmNoSpacing along the second direction in mm
entity_pointsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, non-idempotent), so the bar is lower. The description contributes non-obvious behavior beyond the annotations: 'Replaces the selection' warns that input selection state is consumed, and the angle-based direction semantics explain how geometry is laid out. It stops short of covering undo/reversibility.

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 and outcome, then dense parameter semantics with no filler sentences. Every clause either states behavior or defines a parameter's role.

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, return values need no explanation, and annotations cover safety. The description is nearly complete for a 7-parameter mutation tool; the only real gap is that it never states what happens to the original entities or whether the pattern is one grouped feature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is a moderate 57%, and the description compensates meaningfully: it explains that entity_points is one point per entity, that count_x copies are spaced spacing_x_mm apart along a direction rotated angle_x_deg from sketch X, and that count_y/spacing_y_mm/angle_y_deg form an optional second direction. That relational meaning is not derivable from the bare property titles.

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?

The description names a specific verb and resource ('Repeats sketch entities of the open sketch') and adds scope ('in a row or a grid'), which implicitly contrasts with the circular-pattern siblings. It does not explicitly distinguish itself from the feature-level 'linear_pattern' sibling, which is the main source of ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: 'of the open sketch' tells the agent a sketch must be open, and the example ('a row of holes before one cut') suggests a pre-feature patterning workflow. There is no explicit when-not guidance and no routing statement against sketch_circular_pattern or linear_pattern.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.