Skip to main content
Glama

codex_archive

Destructive

Archive or restore an idle conversation and its native descendants while retaining transcripts, so you can declutter active sessions without losing history.

Instructions

Archive or restore an idle conversation and its native descendants. Transcripts are retained.

Input Schema

NameRequiredDescriptionDefault
actionNoarchive
task_idYesTask id
request_idNoKey for identical retries
operation_idNoAlias of request_id

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: it discloses cascading scope ('and its native descendants') and that transcripts are retained, which materially softens the destructiveHint=true warning by clarifying data is not purged. It still omits permissions, visibility effects after archiving, and how retries interact with the non-idempotent hint.

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?

Two short sentences, front-loaded with the action and resource, with the retention note placed immediately after as the key reassurance. No wasted wording.

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 destructive, cascading mutation with an output schema and safety annotations already supplied, the description covers the two non-obvious facts (descendant cascade, transcript retention). Minor gaps remain around post-archive visibility and permissions, but nothing essential to invoking 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?

Schema coverage is 75%, so the schema largely documents the parameters; the description only loosely maps 'archive or restore' onto the action enum and says nothing about request_id/operation_id retry-key semantics or the task_id requirement. Baseline 3 applies where the schema does the heavy lifting.

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?

Names a specific verb pair (archive/restore) and resource (a conversation plus its native descendants), and adds the 'idle' precondition. It does not distinguish itself from nearby siblings such as codex_delete or codex_compact, so an agent must infer the boundary.

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?

The 'idle conversation' phrasing implies a precondition for use and the action enum implies the restore direction, but there is no explicit when/when-not guidance and no named alternative for related operations like delete or compact.

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