Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Copy a pattern piece

clo_copy_pattern

Duplicate a pattern piece and place the copy at a specified 2D center point, with optional horizontal or vertical mirroring to create mirrored parts such as a right sleeve from a left one.

Instructions

Duplicate a pattern piece, placing the copy's centre at a position in the 2D window. Optionally mirror the copy, e.g. to make a right sleeve from a left one. Returns the new piece's index.

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": {
      "pattern_index": "<pattern_index>",
      "center": "<center>"
    },
    "name": "clo_copy_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoMirror the copy.
nameNoName for the copy.
centerYesCentre of the copy in the 2D window (mm).
pattern_indexYesZero-based pattern index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/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 burden. It does disclose useful behavior — a new piece is created at the given centre, it can optionally be mirrored, and the return value is the new piece's index — but says nothing about whether the source piece is untouched, whether seams/internal shapes/attachments are copied, or what happens on an invalid pattern_index.

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?

Two sentences plus a short return clause, front-loaded with the core action and with zero filler. Each clause — placement, mirroring, return value — carries distinct information.

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?

For a four-parameter creation tool with a nested center object and full schema coverage, this is nearly complete: placement, optional mirroring, and the return value are all covered. What is missing is side-effect disclosure (what the copy inherits, whether the original changes), which matters for an unannotated mutation tool.

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 baseline is 3. The description adds little beyond the schema for center and name, though the mirror example does clarify the intent of the flip enum more than the bare enum values do; that gain is modest.

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 opens with a specific verb and resource ('Duplicate a pattern piece') and adds placement semantics (copy's centre at a 2D position). It is clearly distinct from edit/delete/create siblings, though it never names those siblings to reinforce the boundary.

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?

Guidance is limited to the flip option, where a concrete use case is given ('make a right sleeve from a left one'). There is no statement of when to prefer this over clo_create_patterns or clo_edit_pattern, and no prerequisites such as needing a loaded project.

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