Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

linear_pattern

Repeats one or more features in a straight line at fixed spacing for hole rows, fin arrays, or bolt grids.

Instructions

Pattern (patrón lineal) features in a single straight line.

Repeats one or more existing features along a direction at fixed spacing — the autoparts default for hole rows, fin arrays, and bolt grids. Single-direction only in v1; the second-direction (rectangular grid) variant is deferred since junior designers rarely use it.

Args: feature_names: Names of features to pattern. Pass exact names from get_active_part_info — e.g. ["Cortar-Extruir1"] for a single hole, ["Cortar-Extruir1", "Saliente-Extruir2"] for a hole + boss pair. direction_reference: Name of the entity defining the pattern direction. Easiest source: an "Eje1" name returned by a prior create_reference_axis call. Also accepted: a linear edge name (e.g. "Arista<1>@Pieza1") or a sketch-line name. Names are locale-sensitive. spacing_mm: Distance between consecutive instances in mm. Must be positive. count: Total number of instances INCLUDING the original (must be ≥ 2). For 5 holes total, pass count=5 — the original feature counts as instance #1. reverse: Flip the pattern direction along the reference. Default (False) follows the SW-default direction; pass True if the pattern goes the wrong way.

Returns the new pattern Feature with name (e.g. "LPattern1"), type ("linear_pattern"), and dimensions (D1=spacing, Num=count).

Example — 5 holes spaced 15 mm apart along an existing axis: eje = create_reference_axis("Arista<1>@Pieza1") # use a long edge linear_pattern(["Cortar-Extruir1"], eje["name"], spacing_mm=15.0, count=5)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
reverseNo
spacing_mmYes
feature_namesYes
direction_referenceYes
Behavior3/5

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

With no annotations, the description carries a heavy burden. It discloses that the tool returns a new pattern feature with name, type, and dimensions, and describes the behavior of parameters (spacing must be positive, count includes original, reverse default false). However, it does not warn about failure modes (e.g., invalid feature names or direction references) or clarify whether the original features are modified.

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 well-structured with clear Args, Returns, and an Example section. It is concise yet thorough, every sentence adds value, and it is front-loaded with the tool's purpose.

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 5 parameters, no schema descriptions, and no output schema, the description provides solid coverage. It explains the return format (name, type, dimensions) and includes an example. However, it lacks details on error handling or edge cases, such as what happens if the direction reference is invalid or if pattern instances exceed limits.

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

Parameters5/5

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

The input schema has 0% coverage, so the description must fully define each parameter. It does so comprehensively: 'feature_names' lists exact names from get_active_part_info, 'direction_reference' provides sources (Eje1, edges, sketch lines) with locale-sensitivity, 'spacing_mm' must be positive, 'count' includes original and must be ≥2, 'reverse' defaults false. This adds significant meaning beyond the schema.

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 that the tool patterns features in a straight line, using specific verbs like 'Repeats' and providing concrete examples (hole rows, fin arrays, bolt grids). It distinguishes itself from siblings like 'circular_pattern' by specifying 'single straight line' and mentioning that the second-direction variant is deferred.

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 explains when to use this tool (single-direction patterns) and notes that the second-direction variant is not available in v1. It provides an example usage but does not explicitly mention when not to use it or suggest alternative tools for other pattern types.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/solidworks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server