Skip to main content
Glama

codex_rename

Destructive

Renames an owned native conversation by task ID, so you can give it a clearer, more useful name.

Instructions

Rename an owned native conversation.

Input Schema

NameRequiredDescriptionDefault
nameYes
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

C2.8/5.0
Behavior2/5

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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is known without the description. The description adds only the ownership constraint; it says nothing about the old name being lost, whether the change is reversible via codex_revert, or how the request_id/operation_id retry alias interacts with a non-idempotent write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single eight-word sentence with zero redundancy and the object front-loaded, but the brevity is under-specification rather than economy; nothing about scope, prerequisites, or the idempotency alias is conveyed.

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

Completeness2/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 not be explained, but this is a destructive, non-idempotent mutation with a four-parameter schema including a mutually-exclusive retry-key pair, and the description addresses none of that risk or structure. It is too thin for the tool's complexity.

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 most parameters are already documented in the schema (task_id, request_id, operation_id), and the baseline of 3 applies. The description adds no meaning for 'name' (which has no schema description) or for the anyOf requirement that exactly one of request_id/operation_id be supplied.

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?

The description pairs a specific verb ('Rename') with a specific resource ('an owned native conversation'), so an agent knows the operation is a title/name change on a conversation it owns. It does not differentiate from siblings such as codex_archive, codex_fork, or codex_get, and 'native' is unexplained, but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose rename over alternatives like codex_archive or codex_fork, nor any stated prerequisites beyond the adjective 'owned'. The agent must infer that only the caller's own conversations are eligible.

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