Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

linear_pattern

Pattern one or more features along model axes in one direction or as a grid. Set count, spacing and direction to place repeated instances and get a warning if they fall outside the body.

Instructions

Pattern one or more features along the model axes, in one direction or two (a grid). count includes the original. Warns if new instances fall outside the body.

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": {
      "count": "<count>",
      "spacing": "<spacing>",
      "direction": "<direction>"
    },
    "name": "linear_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
countYesInstances along direction, including the original
count2NoInstances along direction2, including the original
spacingYesDistance between neighbouring instances
featuresNoFeature names from list_features, e.g. ['Cut-Extrude1']. Default: the last solid feature.
spacing2NoSpacing along direction2 (needed with count2 above 1)
directionYesPattern direction in model axes
direction2NoOptional second direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses counting semantics ('count includes the original') and failure-surface behavior ('Warns if new instances fall outside the body'), but says nothing about whether the operation is reversible, what it returns, or what happens if the feature list is empty.

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?

Three tight sentences with the core action front-loaded and no filler. The clipped fragment style ('count includes the original') is efficient, though slightly telegraphic for an agent parsing semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the essential concept but omits what a caller needs to know about results, failure modes, and prerequisites (e.g. that features must come from list_features, or whether spacing2 is validated). Adequate but with clear gaps.

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%, so the schema already documents every parameter including enums and defaults. The description's 'count includes the original' and grid hint restate rather than extend the schema, 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?

The description gives a specific verb and resource ('Pattern ... features along the model axes') plus the scope ('one direction or two (a grid)'), which implicitly separates it from the circular_pattern sibling. It stops short of explicitly contrasting with that sibling, so a 4 rather than a 5.

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 is only implied: the 'one direction or two (a grid)' phrase tells the agent the tool covers both linear and grid patterns, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. circular_pattern).

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