Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Get fabric details

clo_get_fabric
Read-only

Retrieves one fabric's name, material, physical properties, width, base color, and texture paths by zero-based index to inspect fabric data in a CLO 3D project.

Instructions

Properties of one fabric in the project: name, material and physical information, width, base colour and texture paths.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fabric_index": "<fabric_index>"
    },
    "name": "clo_get_fabric"
  }
}

Input Schema

NameRequiredDescriptionDefault
fabric_indexYesZero-based fabric index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes the safety profile, and the description adds value by disclosing which properties come back. It says nothing about behavior for an out-of-range fabric_index, whether 'physical information' is simulated or authored data, or how texture paths are formatted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence, front-loaded with the resource and immediately followed by the returned fields. It is a noun fragment rather than a complete clause, but no words are wasted.

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 single-parameter read-only tool with no output schema, listing the returned properties effectively substitutes for an output description, which is the main thing an agent needs. The remaining gap is discoverability of the fabric_index, which is left unaddressed.

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 100% and the single parameter is documented as a zero-based fabric index, so the schema does the heavy lifting. The description adds nothing about how indices map to project fabrics or how to obtain them; baseline 3 applies.

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 names a specific resource (one fabric in the project) and enumerates what is returned: name, material and physical information, width, base colour and texture paths. That is clear enough to separate it from mutation siblings like clo_add_fabric or clo_edit_fabric, though it never explicitly says 'read/retrieve' or names a contrasting sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus clo_get_scene, clo_get_patterns or clo_get_fabric-adjacent tools, and no prerequisites such as where a valid fabric_index comes from. Usage is only inferable from the returned-field list.

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