Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Start a new project

clo_new_project
Destructive

Clears the current garment in CLO 3D and starts a new project. Export unsaved .zprj work first, because the reset discards unsaved changes.

Instructions

Clear the current garment and start a new one. Unsaved work is lost; export a .zprj first if it matters.

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_new_project"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

The destructiveHint annotation already flags this as destructive, and the description earns credit for specifying exactly what is destroyed (the current garment) and that unsaved work is lost. It does not say whether the reset is recoverable via undo, which would matter for a destructive action.

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 short sentences, no filler, with the destructive effect stated before the mitigating advice. Every clause carries information an agent needs.

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 zero-param destructive tool with no output schema, the definition covers what happens and how to mitigate it. The only meaningful omission is whether the reset can be reversed with undo.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to add or omit.

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 concrete verb and resource: clear the current garment and start a new one. An agent can distinguish it from clo_open_file or clo_get_scene without opening any schema, though it never names a sibling for explicit contrast.

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 clear usage condition and a pre-condition: export a .zprj first if the work matters, which implicitly routes to the export tool. There are no explicit exclusions (e.g., 'use clo_open_file instead if you want an existing project'), so it falls short of a 5.

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