Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

List or change colorways

clo_colorways

List a CLO 3D project's colorways, then copy, rename, or switch the active one to manage color variants in an open session.

Instructions

List the project's colorways, and optionally add one by copying, rename one, or switch the active one. With no arguments it only lists. Operations run in the order copy, rename, switch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clo_colorways"
  }
}

Input Schema

NameRequiredDescriptionDefault
renameNo
copy_fromNoCreate a new colorway as an unlinked copy of this one.
switch_toNoMake this the active colorway.

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 carries the burden of behavioral disclosure. It usefully states that operations run in order copy, rename, switch, but it does not explain permissions, whether changes are reversible, what copying preserves, or what the tool 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 dense sentences front-load the primary listing behavior and then cover optional mutations and ordering. There is no redundant wording or unnecessary setup.

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 tool with a nested parameter object, multiple optional mutations, and no annotations or output schema, the description leaves out return behavior and important mutation semantics. It is adequate for selecting and invoking the tool, but not fully complete for safe operation.

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 coverage is 67%, and the schema already documents copy_from, switch_to, and the nested index. The description maps the optional operations to those parameters but adds little parameter-level detail beyond the operation ordering.

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?

The description names a specific resource (the project's colorways) and specific operations: list, copy, rename, and switch. It also states the no-argument behavior, making the tool's purpose unambiguous.

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?

It clearly explains the default no-argument listing behavior and that copy, rename, and switch can be combined in a defined order. It does not give explicit exclusions or prerequisites, but the usage conditions are clear enough for a zero-required-parameter tool.

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