Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Edit a pattern piece

clo_edit_pattern

Modify an existing pattern piece by changing only selected properties, such as name, position, flip, fabric, layer, grain, mesh density, or 3D visibility and freeze state.

Instructions

Change properties of an existing pattern piece. Set only the fields you want changed: rename, move in the 2D window, flip, re-place on the avatar, change fabric, layer, grain, mesh density, or freeze/hide it in 3D.

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>"
    },
    "name": "clo_edit_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoMirror the piece in place.
nameNo
layerNoCollision layer; higher layers sit outside lower ones.
centerNoMove the piece so its centre is here in the 2D window (mm).
freezeNoFreeze the piece so simulation does not move it.
hide_3dNoHide the piece in the 3D window.
fabric_indexNoZero-based fabric index.
pattern_indexYesZero-based pattern index.
grain_directionNoGrain line angle in degrees.
arrangement_pointNoArrangement point on the avatar, by name (e.g. "Body_Front_Center_2", "Leg_Skirt_Back", "Arm_Outside_1_L") or index. See clo_list_arrangement_points.
particle_distanceNoMesh resolution in mm (default 20; smaller is finer and slower).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; "Change" establishes a mutation, and the selective-field instruction implies that omitted properties are left alone. It usefully distinguishes 2D, avatar, and 3D effects, but does not explain persistence, simulation consequences, failure behavior, or the result of a successful call.

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 front-load the resource and partial-update rule, then compress the broad capability set into one useful list. Despite the list's length, there is no filler or redundant setup.

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 an 11-parameter edit tool, the rich schema supplies required indexing, constraints, units, and the arrangement-point lookup, while the description supplies the key existing-piece and selective-update model. It is sufficient for correct selection and invocation in most cases, but the absence of annotations and an output schema leaves behavioral and result expectations less complete.

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 91%, so units, index bases, defaults, and individual field meanings are already well documented. The description adds valuable cross-parameter patch semantics and maps the optional fields to user-facing goals, although most of its capability list restates rather than extends the schema.

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 opening sentence gives a specific verb and resource—"Change properties of an existing pattern piece"—and the follow-up identifies the 2D, avatar, fabric, and 3D operations in scope. This separates it conceptually from creation and fabric-focused siblings, but it does not explicitly delineate those alternatives.

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?

"Set only the fields you want changed" gives clear guidance for partial edits, while "existing pattern piece" establishes the intended situation. There are no explicit when-not conditions or sibling-routing guidance for narrower operations.

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