Skip to main content
Glama

Linear Pattern

linear_pattern

Repeats a PartDesign feature linearly along an axis or edge, setting total length and occurrence count to create patterned copies in FreeCAD.

Instructions

Repeat a PartDesign feature linearly along a direction.

direction: 'X'|'Y'|'Z' for body origin axes, or {handle, edge: tag|'EdgeN'} for an edge-aligned direction. length: total span (mm) covered by the pattern. occurrences: number of copies (>=2). Includes the original.

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": {
      "feature": "<feature>"
    },
    "name": "linear_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLinearPattern
lengthNo
featureYes
reversedNo
directionNoX
workspaceNoRun this call in this named workspace
occurrencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds a genuinely useful semantic clarification (occurrences includes the original, length is the total span), but it never says what gets created in the feature tree, whether the original feature is modified, or how failure behaves.

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 purpose sentence followed by three tight parameter notes; no filler. Minor structural weakness is that parameter prose is mixed into the main body rather than clearly separated, but it stays short and readable.

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

Completeness2/5

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

For a 7-parameter mutation tool with a required 'feature' argument, the description leaves the required argument undefined and omits 'reversed' entirely, which an agent could easily mis-set. Direction's object form is described but without any example of the handle acquisition flow that resolve_edge/list_edges siblings imply.

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 14%, so the description must compensate and it does for three parameters: direction (axis enum vs {handle, edge: tag|'EdgeN'} form), length (total span in mm, not per-gap), and occurrences (>=2, inclusive of original). However, the one required parameter 'feature' is never explained, and 'reversed', 'name', and 'workspace' are untouched.

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?

Specific verb + resource + scope: 'Repeat a PartDesign feature linearly along a direction.' An agent immediately knows this is a linear pattern operation. It does not explicitly contrast with its closest siblings polar_pattern or mirrored, so it falls short of 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 by the verb 'Repeat ... linearly'; there is no statement of when to pick this over polar_pattern or mirrored, no prerequisites (must a feature already exist?), and no note on whether this is pattern-as-feature or pattern-as-copy.

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