Skip to main content
Glama
4dhxm

codex-mcp-server

by 4dhxm

codex_interrupt

Interrupt a running turn on an active thread to halt an ongoing autonomous coding task.

Instructions

Alias for codex_interrupt_turn. Interrupt a running turn on an active thread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdYesThe thread ID currently executing a turn.
Behavior2/5

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

No annotations provided; description only states it interrupts a running turn. Fails to disclose side effects, state changes, or irreversibility. Significant gap for a potentially destructive action.

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?

Extremely concise with no wasted words. Two sentences front-load the core purpose and alias relationship.

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?

Lacks output schema, behavioral details, and usage guidance. For a turn-interruption tool, missing critical context like whether it is reversible, any effects on thread state, or prerequisites.

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% for the single parameter (threadId). The description adds no additional semantic value beyond the schema, so baseline 3 applies.

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?

Clearly states it interrupts a running turn and notes it is an alias for codex_interrupt_turn. However, it does not differentiate from siblings; since it's an alias, purpose is clear but not uniquely distinguished.

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?

No guidance on when to use this tool versus alternatives. Merely states it's an alias without context on when interrupting a turn is appropriate or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/4dhxm/codex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server