Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Run the drape simulation

clo_simulate

Run garment drape simulation for a set number of steps in CLO 3D, with optional quality preset and arrangement reset, then capture a screenshot to inspect the settled result.

Instructions

Simulate the garment for a number of steps. CLO is busy until it finishes; follow with clo_screenshot to see the result. Around 100-200 steps settles a simple garment.

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

Input Schema

NameRequiredDescriptionDefault
stepsNoSimulation frames to run (default 100).
qualityNoSwitch the project's simulation preset first: normal, animation (stable), fitting (accurate fabric, slow) or fast-gpu. Leave unset to keep the current one.
timeout_sNoSeconds to wait for CLO before giving up.
reset_arrangementNoPut all pieces back at their arrangement positions before simulating, to recover from a tangled drape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the critical trait that 'CLO is busy until it finishes' — an agent knows not to issue concurrent calls. It also implies recovery semantics via reset_arrangement and bounds the wait through timeout_s, but says nothing about what the call returns, whether the new drape persists across sessions, or whether the run is abortable.

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?

Three short sentences, front-loaded with the action, then the blocking caveat, then the practical tuning hint. Nothing is filler and the ordering matches the order an agent needs the information.

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 blocking, all-optional-parameter tool with no output schema, the description covers the essentials: what it does, that it monopolizes CLO, how many steps to use, and what to call next. It is let down only by not describing the result of a run (whether it reports convergence or failure) or the effect of changing the quality preset.

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 all four parameters are already documented, setting the baseline at 3. The description does add one genuinely useful heuristic ('around 100-200 steps settles a simple garment') that gives scale to the otherwise abstract steps parameter, but it says nothing about quality, timeout_s, or reset_arrangement beyond what the schema already provides.

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?

The description states a specific verb and resource: 'Simulate the garment for a number of steps', which is more precise than the title alone and tells an agent this advances the drape solver rather than editing geometry. It also positions the tool in a workflow by naming clo_screenshot as the follow-up, though it does not explicitly contrast itself with other mutating siblings.

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 gives concrete usage guidance: run around 100-200 steps for a simple garment, then check with clo_screenshot. There is no explicit when-not-to-use or statement about which sibling to prefer for other simulation needs, so it falls short of the top band.

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