Skip to main content
Glama

codex_compact

Destructive

Request native history compaction for an idle conversation and poll completion events; may consume model usage.

Instructions

Request native history compaction for an idle conversation; may consume model usage. Poll completion events.

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, so the definition is not the sole carrier of risk, but the description adds genuinely new behavior context: it may consume model usage (a cost signal) and it is asynchronous, requiring polling for completion. It does not spell out what 'compaction' destroys or rewrites in the history, which for a destructive operation is a notable omission.

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?

Two compact clauses, front-loaded with the action and the precondition. The telegraphic final fragment 'Poll completion events' is efficient but slightly clipped, leaving the target tool unnamed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers cost and async completion. However, for a destructive, non-idempotent operation it should state what history is affected, what happens on a non-idle conversation, and how retries with request_id interact with idempotentHint=false.

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%, so each parameter (task_id, request_id, operation_id alias) is already documented and the 3 baseline applies. The description adds nothing about retry semantics or the request_id/operation_id aliasing, so it neither compensates nor detracts.

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 and resource: 'Request native history compaction'. The scope qualifier 'for an idle conversation' further narrows it, so it is not a tautology. It stops short of distinguishing itself from other history-manipulating siblings (e.g. codex_history, codex_revert), so it does not reach a 5.

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?

'for an idle conversation' implies a precondition, but it never says what to do if the conversation is not idle, nor does it name an alternative for a running session. 'Poll completion events' implies a follow-up step but leaves the agent to infer which tool (likely codex_events) performs that polling.

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