Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Show or mark the edit history

clo_history

List undoable and redoable CLO changes newest first with their originating tool calls; add a named checkpoint to mark a state so clo_undo can return to it.

Instructions

List the changes that can be undone or redone, newest first, with the tool call that made each. Pass checkpoint to mark the current state with a label (for example before trying a design variation), so clo_undo can return to it by name. History covers this CLO launch and keeps the most recent 25 changes.

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

Input Schema

NameRequiredDescriptionDefault
checkpointNoLabel for a checkpoint of the current state, e.g. "before sleeves".

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?

With no annotations, the description carries the burden and does real work: it discloses ordering (newest first), scope ('this CLO launch'), a retention limit ('most recent 25 changes'), and the checkpoint lifecycle. It leaves out what happens when the 25-entry limit evicts older changes or whether multiple checkpoints may coexist.

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 sentences, each earning its place, with the primary list behavior front-loaded and the optional-parameter mode second. No restatement of the name or title, no filler.

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 tool with no output schema, it covers ordering, scope, retention, and the cross-tool contract that makes checkpoint useful. Nothing an agent needs in order to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema: checkpoint marks the current state and is later addressable by name via clo_undo. That downstream contract is not expressible in the schema and materially helps an agent decide whether to set the parameter.

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 changes that can be undone or redone') plus the return shape ('newest first, with the tool call that made each'), and adds the secondary checkpoint-marking mode. An agent can distinguish this from clo_undo/clo_redo without opening either schema.

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 explicit when-to-use guidance for the checkpoint parameter ('before trying a design variation') and ties it to the sibling it feeds ('so clo_undo can return to it by name'). It does not state when to prefer clo_undo or clo_redo directly, so it stops short of full alternative routing.

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