Skip to main content
Glama

codex_fork

Destructive

Fork an idle owned conversation at a chosen turn while preserving project boundaries without starting work or continuing a goal.

Instructions

Fork an idle owned conversation, optionally through a selected turn. Keeps project boundaries; does not start work or automatically continue a goal.

Input Schema

NameRequiredDescriptionDefault
nameNo
task_idYesTask id
request_idNoKey for identical retries
last_turn_idNo
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

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the description's job is to add context, which it does: it discloses that project boundaries are preserved and, most importantly, that forking does not trigger work or auto-continue a goal. It does not explain why a fork is flagged destructive (e.g. locking or consuming turn state) or what happens to the source beyond 'keeps project boundaries', leaving part of the declared risk unaccounted for.

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 sentences with no filler; the action comes first and the behavioral caveat second. Every clause carries information an agent needs before invoking the tool.

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?

With an output schema present, return values need not be explained, and the description covers the essential preconditions (idle, owned) and post-conditions (no work started, goal not continued, project boundary preserved). It is slightly thin on the destructive/idempotency semantics that the annotations imply for a non-idempotent write.

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 60% and the description adds meaning to two of the five parameters: 'through a selected turn' clarifies last_turn_id, and the conversation framing maps to task_id. The 'name' parameter and the request_id/operation_id retry aliasing are left entirely to the schema, so this is baseline-level rather than compensating for the coverage gap.

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?

States a specific verb and resource: 'Fork an idle owned conversation', scoped further by 'optionally through a selected turn'. This is precise enough that an agent can distinguish forking from copying, resuming, or starting, though no sibling tool is named as a contrast point.

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?

The precondition 'idle owned conversation' makes the eligibility condition explicit, and 'does not start work or automatically continue a goal' is a useful boundary statement about what the caller must do afterward. No alternative sibling (e.g. codex_resume, codex_start) is named as a routing option, so the guidance stops short of full when/when-not routing.

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