Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Add a fabric

clo_add_fabric

Load a .zfab or .jfab fabric file into a CLO project's fabric list, then assign it to selected pattern pieces or all patterns.

Instructions

Load a fabric file (.zfab, .jfab) into the project's fabric list and optionally assign it to pattern pieces. CLO's bundled fabrics are in ~/Documents/clo/CLO Assets/Fabric (denim, jersey knits, organza, velvet, ...).

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": {
      "file_path": "<file_path>"
    },
    "name": "clo_add_fabric"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the fabric file.
assign_to_patternsNoPattern indices to give this fabric to, or "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it discloses that the file is added to a persistent project fabric list and that assignment to pattern pieces is optional. It does not say what happens on a duplicate path, whether the file must exist, whether the operation is undoable, or what a failure looks like.

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?

Two tight sentences with no filler, front-loaded with the action and formats. The bundled-assets sentence is useful but sits slightly awkwardly as a parenthetical aside.

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

Completeness3/5

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

There is no output schema, and the description never indicates what comes back from the call (e.g., a fabric identifier that later tools such as clo_assign_fabric or clo_edit_fabric would need). For a two-parameter mutation tool the rest is adequately covered.

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 100%, so the baseline is 3, but the description earns extra credit by naming the accepted formats (.zfab, .jfab) and pointing at concrete example asset locations, which the schema does not say. 'Assign it to pattern pieces' also reinforces the meaning of assign_to_patterns beyond the schema wording.

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 (load/add) plus the resource (fabric file into the project's fabric list) and names the accepted extensions, so it is distinguishable from clo_edit_fabric or clo_assign_fabric at a glance. It stops short of explicitly naming which sibling to use instead when assignment is the only goal.

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?

The word 'optionally assign' implies that assignment is secondary here, hinting that pure assignment is a separate operation, but no alternative tool is named and no when-not-to-use condition is given. The mention of CLO's bundled fabric directory is helpful context but is not usage guidance.

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