Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Assign a fabric to patterns

clo_assign_fabric

Assign an existing project fabric to selected pattern pieces or all pieces, with optional colorway scope, to update garment materials before simulation or export.

Instructions

Apply a fabric already in the project to pattern pieces.

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": {
      "fabric_index": "<fabric_index>",
      "pattern_indices": "<pattern_indices>"
    },
    "name": "clo_assign_fabric"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoWhich colorways receive the change (default all-colorways-linked).
fabric_indexYesZero-based fabric index.
pattern_indicesYesPattern indices, or "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a mutation tool, and it discloses almost nothing: not whether existing fabric assignments are replaced, not that the change can span multiple colorways (documented only in the schema's scope enum), and not whether it is undoable. The one useful signal, that the fabric must already exist, is present but thin for a write operation.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though economy shades into under-specification given the tool's mutation semantics.

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 three-parameter mutation tool with no annotations, no output schema, and a non-trivial scope enum governing which colorways change, the description should say more. It leaves the colorway side effect, overwrite behavior, and required preconditions entirely to the schema and inference.

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 100%, so fabric_index, pattern_indices, and scope are all documented in the input schema, and the baseline is 3. The description mentions none of them and adds no meaning beyond the schema, notably omitting the colorway-scoping behavior that is the least obvious parameter.

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?

States a specific verb+resource pair: "Apply a fabric... to pattern pieces." The qualifier "already in the project" implicitly separates it from clo_add_fabric, which brings new fabrics in, so an agent can broadly distinguish the two without opening either schema. It stops short of naming that sibling explicitly.

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 phrase "a fabric already in the project," which signals this is for existing assets rather than creating them. There is no explicit when-to-use statement, no mention of a prerequisite (pattern and fabric must already exist), and no named alternative such as clo_add_fabric or clo_edit_fabric.

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