Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

List avatar arrangement points

clo_list_arrangement_points
Read-only

Lists arrangement points around the loaded avatar by index and name so you can place pattern pieces near a body part before simulation; returns nothing if no avatar is loaded.

Instructions

List the arrangement points around the loaded avatar (index and name), which place pattern pieces near a body part before simulation. Returns nothing if no avatar is loaded.

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

Input Schema

NameRequiredDescriptionDefault
filterNoOnly names containing this text, case-insensitive, e.g. "skirt", "arm", "body_front".

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?

Annotations only declare readOnlyHint=true, so safety is covered, and the description adds the non-obvious state dependency 'Returns nothing if no avatar is loaded' along with what each entry contains. That is real behavioral context a caller would otherwise discover only by failing.

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?

One well-formed sentence that front-loads the resource and folds the return contract and edge case into the same breath. No filler, no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read-only listing with no output schema, the description covers purpose, return fields, and the empty-result condition. Nothing an agent needs to call it correctly is missing.

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?

The single optional 'filter' parameter is fully documented in the schema (100% coverage) with examples, and the description says nothing about it. Baseline 3 is appropriate since the schema carries the parameter burden.

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?

States a specific verb and resource ('List the arrangement points around the loaded avatar') and adds the return shape ('index and name') plus the domain function of these points. An agent knows exactly what it will get back without opening any other tool.

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?

Usage is implied by the clause 'before simulation' and 'place pattern pieces near a body part', which indicates when the data is relevant. There is no explicit when-not guidance or named alternative for discovering placement targets.

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