Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

CLO status

clo_status
Read-only

Verify that CLO 3D is running with the bridge loaded before other actions. Returns CLO version, open project, and counts of patterns, fabrics, colorways, and avatars.

Instructions

Check that CLO is running with the bridge loaded. Returns CLO version, open project, and counts of patterns, fabrics, colorways and avatars. Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds real context beyond that: it verifies bridge loading and reports concrete state (version, open project, entity counts) rather than mutating anything. It does not discuss failure behavior when CLO is not running, which would have made it 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?

Three short sentences, front-loaded with the purpose, then the returns, then the ordering instruction. Every sentence earns its place with no redundancy.

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?

With no parameters, no output schema, and only a readOnly annotation, the description carries the necessary burden by enumerating the return payload in plain language. An agent knows what the call does, what it gets back, and when to make it.

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 there is no argument semantics to explain and the baseline is 4. The description correctly spends no words on inputs and instead covers the return contents.

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?

The description gives a specific verb ('Check') plus the exact resource state being verified ('CLO is running with the bridge loaded') and enumerates what is returned: version, open project, and counts of patterns, fabrics, colorways and avatars. Its 'Call this first' framing also positions it distinctly as the preflight tool relative to the many action-oriented 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 explicit sequencing guidance with 'Call this first', which tells an agent when to reach for this tool before any other. It stops short of naming when-not-to-use cases or an alternative when the check fails (e.g., clo_stop_bridge or clo_new_project), so it is clear but not fully opinionated.

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