Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Edit a fabric

clo_edit_fabric

Rename a project fabric, set its base colour to tint textures, or swap in a .zfab file while keeping existing assignments intact. Update only the fields you need.

Instructions

Change a fabric in the project: rename it, set its base colour (tints any texture), or replace it with a different fabric file while keeping its assignments. Set only the fields you want changed.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNoBase colour as hex, e.g. "#C0392B". Applied to front, back and side.
fabric_indexYesZero-based fabric index.
replace_with_fileNoAbsolute path of a .zfab file to replace this fabric with.

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 supplied, the description carries the full burden. It usefully discloses that the change is partial, that replacing a file preserves existing assignments, and that colour tints textures — non-obvious side effects. It omits reversibility/undo, error behavior for a bad index or missing .zfab file, and what a successful call returns.

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-loaded with the operation set, and the closing partial-update rule earns its place by preventing the agent from blanking unset fields. No redundant restatement of the schema.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers what can change and the update semantics but leaves out failure modes, whether changes are undoable, and what a call yields. Adequate, but the burden not covered by structured fields remains significant.

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 75% and already documents fabric_index and color format. The description adds genuine meaning beyond the schema: the partial-update contract for all four fields and the assignment-preservation guarantee for replace_with_file, plus it covers the otherwise undocumented 'name' parameter as a rename.

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 plus resource and enumerates the three operations (rename, set base colour, replace file), so an agent knows exactly what the tool can change. It does not name the sibling it is differentiated from (clo_add_fabric / clo_assign_fabric), leaving that inference to the agent.

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?

"Set only the fields you want changed" establishes partial-update usage, and 'while keeping its assignments' hints at when to replace rather than re-assign. There is no explicit when-to-use vs. clo_add_fabric or clo_assign_fabric, and no stated prerequisites such as the fabric index needing to exist.

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