Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Open or import a file

clo_open_file

Opens a CLO file by absolute path; .zprj projects replace the current scene and discard unsaved work, while avatars, garments, fabrics, meshes, and patterns are added using defaults.

Instructions

Open a file in CLO by path. A project (.zprj) replaces the current scene, discarding unsaved work. Avatars (.avt), garments (.zpac), fabrics (.zfab), DXF patterns, OBJ/FBX/glTF meshes and other supported formats are added to it using CLO's defaults. Bundled avatars are in ~/Documents/clo/CLO Assets/Avatar.

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": {
      "file_path": "<file_path>"
    },
    "name": "clo_open_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path of the file to open.
timeout_sNoSeconds to wait for CLO before giving up.
add_to_sceneNoFor .zprj only: add the project's contents to the current scene instead of replacing it (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it warns that a .zprj discards unsaved work, explains that other formats are added using CLO's defaults, and points to the bundled asset location. It omits what a failure or timeout returns and whether the call blocks, which keeps it from 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 tight sentences, front-loaded with the core action, then the destructive .zprj warning, then format handling and the asset hint. Nothing is repeated or padding.

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 3-parameter tool with no output schema and no annotations, the description covers the risky part (scene replacement), format breadth, and defaults. Only return/error behavior and timeout semantics are left unaddressed, a minor gap given the schema documents timeout_s.

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 file_path, timeout_s, and add_to_scene are already documented. The description reinforces format-dependent behavior but adds no syntax, path-format, or timeout guidance beyond the schema, so the baseline 3 applies.

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 ("Open a file in CLO by path") and then distinguishes two distinct behaviors: .zprj replaces the scene while other formats are added to it. An agent can immediately tell what the tool does and how it varies by input, which no sibling tool name duplicates.

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?

Gives clear context for when this is the right call: you have a path and want it loaded into CLO, with the .zprj vs. asset-format branch spelled out. It stops short of naming alternatives or exclusions (e.g., when to prefer clo_new_project or clo_add_fabric), so it lands at clear-context-but-no-routing.

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