Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Describe the CLO scene

clo_get_scene
Read-only

Summarise the open CLO 3D project in one call: pattern pieces, fabrics, colorways, avatars, and simulation quality for a quick scene overview.

Instructions

Summarise the open project in one call: every pattern piece (index, name, fabric, centre position, size, arrangement point, seam groups), fabrics, colorways, avatars and simulation quality. Use clo_get_patterns for outline points and line indices.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, yet the description still contributes real information: the exact breadth of the snapshot returned, which is the main behavioral unknown for a zero-parameter tool with no output schema. It does not discuss cost, latency, or whether the scene must be loaded/open, which keeps it short of a 5.

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?

Front-loaded with the purpose in the first clause, followed by a parenthetical field list and a single routing sentence. No filler, no restatement of the title, and the alternative-tool hint is placed last where it is least disruptive.

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?

Because there is no output schema, the description carries the burden of describing return content and does so field by field, which is sufficient for an agent to decide whether one call is enough. The only gap is any caveat about the scene needing to be open or the summary being potentially large.

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 no parameters, so there is no parameter semantics to explain and the schema fully covers the input. Baseline 4 applies since nothing is left ambiguous on the input side.

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?

"Summarise the open project in one call" states a specific verb and scope, then enumerates exactly what is included (pattern pieces with index/name/fabric/centre position/size/arrangement point/seam groups, fabrics, colorways, avatars, simulation quality). It is clearly distinguishable from clo_get_patterns, which is scoped to outline points and line indices.

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?

"In one call" signals the tool is for a one-shot overview, and the closing sentence routes the agent to clo_get_patterns for outline points and line indices. That is an explicit alternative with a selecting condition, though it does not say when to prefer other overview-ish siblings such as clo_status or clo_list_arrangement_points.

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