Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Sew pattern lines together

clo_sew

Joins outline lines on pattern pieces to create garment seams in CLO 3D. Submit all seams in one call, using line indices from pattern creation or retrieval.

Instructions

Create seams, each joining an outline line on one piece to an outline line on another (or the same) piece. Pass every seam of the garment in one call. Get line indices from clo_create_patterns or clo_get_patterns. The two lines are joined start-to-start by default; set direction_b false when line B runs the opposite way along the seam, otherwise the seam twists.

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": {
      "seams": "<seams>"
    },
    "name": "clo_sew"
  }
}

Input Schema

NameRequiredDescriptionDefault
seamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4/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 usefully explains the start-to-start default and the twist failure mode when direction_b is wrong, but says nothing about whether existing seams are replaced, whether the operation is reversible, or whether errors are returned per seam or for the whole batch.

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?

Three sentences, front-loaded with the core operation, then the batching rule, then the one non-obvious parameter caveat. No filler, and every sentence conveys actionable 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 single-array-parameter, no-output-schema tool this is nearly sufficient: it defines the operation, the batching contract, index sources, and the main directional pitfall. Missing only failure/duplicate-seam behavior, which matters for a batch mutation.

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?

Effective schema coverage is essentially zero at the top level (the single 'seams' array has no description), so the description must compensate. It does add real meaning for direction_b ('set direction_b false when line B runs the opposite way... otherwise the seam twists') and implies where line indices come from, but direction_a, pattern pairing, and the array-level semantics are left unexplained.

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?

States a specific verb and resource: 'Create seams, each joining an outline line on one piece to an outline line on another (or the same) piece.' That precisely defines the operation and distinguishes it from pattern-creation/editing siblings.

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?

Gives a strong batching rule ('Pass every seam of the garment in one call') and names the prerequisite sources for line indices (clo_create_patterns or clo_get_patterns). It does not state exclusions, e.g. what to do when a seam already exists or when the lines are incompatible.

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