Skip to main content
Glama

codex_interrupt

Destructive

Interrupts a specified active Codex turn and polls until it is interrupted or completed, since acknowledgement alone does not confirm completion.

Instructions

Ask Codex to interrupt the specified active turn. Poll for interrupted/completed; interrupt acknowledgement alone is not completion.

Input Schema

NameRequiredDescriptionDefault
task_idYesTask id
request_idNoKey for identical retries
operation_idNoAlias of request_id
expected_turn_idYes

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?

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the mutating nature is known. The description adds genuinely new behavioral context beyond that: an acknowledgement is not completion, and the agent must poll for a terminal state — a real trap it steers the caller away from. It still does not say what the interrupt does to in-flight work or how failures surface, which keeps it at 4.

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, both front-loaded and purposeful: the action first, then the completion condition. No filler, no repetition of the tool name or annotations.

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 simple, flat four-parameter mutation with an output schema and full annotations, the description covers purpose and the critical polling contract. The remaining gap is retry semantics: the schema offers request_id 'for identical retries' while annotations say idempotentHint=false, and the description does not reconcile that for the agent.

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% (only expected_turn_id lacks a schema description, and request_id/operation_id alias is documented in-schema). The description mentions no parameters at all, so it adds no meaning beyond the schema. Baseline 3 is appropriate given the schema does most of the work.

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 names a specific verb ('interrupt') and a specific target ('the specified active turn'), so an agent knows exactly what the call does. It does not name any sibling tool to contrast with, and the phrase 'Ask Codex to' is slightly indirect, which keeps it below 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?

The description implicitly defines the usage condition (there must be an active turn) and gives explicit post-call guidance: poll for interrupted/completed. However, it never says when to prefer interrupting over alternatives such as codex_respond, codex_send, or codex_revert, and it does not say what to do if the turn is not active.

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