Skip to main content
Glama
codex-mcp-tool

codex-mcp-tool

batch-codex

Destructive

Delegate multiple atomic tasks to Codex for batch processing, enabling repetitive operations, mass refactoring, and automated code transformations.

Instructions

Delegate multiple atomic tasks to Codex for batch processing. Ideal for repetitive operations, mass refactoring, and automated code transformations

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tasks": "<tasks>"
    },
    "name": "batch-codex"
  }
}

Input Schema

NameRequiredDescriptionDefault
ossNoUse local Ollama server
modelNoOptional model override applied to every task. Known: gpt-6.1-sol, gpt-6-astra, gpt-6.1-terra, gpt-6-sol, gpt-6-luna, gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna. If omitted, uses your Codex CLI default (~/.codex/config.toml).
tasksYesArray of atomic tasks to delegate to Codex
searchNoEnable live web search for all tasks using the native --search flag
sandboxNoSandbox mode: read-only, workspace-write, danger-full-accessworkspace-write
timeoutNoMaximum execution time per task in milliseconds
parallelNoExecute independent tasks in parallel
workingDirNoWorking directory for execution
concurrencyNoMaximum parallel Codex processes when parallel=true. Default: min(task count, 4)
stopOnErrorNoStop execution if any task fails
enableFeaturesNoEnable feature flags
disableFeaturesNoDisable feature flags

Output Schema

NameRequiredDescriptionDefault
totalYes
failedYes
resultsYes
skippedYes
successfulYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.7.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile supplied by structured data is strong. The description corroborates side effects only indirectly through phrases such as 'mass refactoring' and 'code transformations', and says nothing about default workspace-write sandboxing, error-stopping behavior, or cost/time implications. With the bar lowered by annotations, partial corroboration earns a 3.

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, front-loaded with the core action and immediately followed by the use cases. Every sentence earns its place, with no boilerplate or repetition.

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?

This is a destructive, open-world batch-execution tool with twelve parameters, and the description never mentions side effects, prerequisites, or how failures are handled. The schema and annotations carry almost all of the burden, leaving the description inadequate 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 description coverage is 100%, and the parameter descriptions handle model names, sandbox modes, concurrency caps, and task structure in detail. The description adds no parameter guidance beyond that, so the baseline of 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?

The description states a specific verb and resource ('Delegate multiple atomic tasks to Codex for batch processing'), which clearly distinguishes it from a single-shot invocation. It does not explicitly name the sibling it differs from (ask-codex), so it falls short of 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 Guidelines4/5

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

It gives clear usage scenarios ('repetitive operations, mass refactoring, and automated code transformations'), which tells an agent when to reach for it. There are no exclusions, prerequisites, or named alternatives, so it is not a 5.

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