Skip to main content
Glama
kky42

codex-as-mcp

by kky42

spawn_agents_parallel

Spawn concurrent Codex agents, each with a specific prompt, to execute tasks in parallel and collect results.

Instructions

Spawn multiple Codex agents in parallel.

Each spawned agent reuses the server's current working directory
(``os.getcwd()``).

Args:
    agents: List of agent specs, each with a 'prompt' entry.
            Example: [
                {"prompt": "Create math.md"},
                {"prompt": "Create story.md"}
            ]

Returns:
    List of results with 'index', 'output', and optional 'error' fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that each spawned agent reuses the server's current working directory (os.getcwd()) and describes the return structure. This adds valuable context beyond the raw function name, though it does not cover all potential side effects or concurrency details.

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?

The description is concise and well-structured: a clear purpose sentence, a behavioral note, and compact Args/Returns sections. Every line earns its place with no redundant information.

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?

The description covers the tool's purpose, parameter shape, and return format, which is sufficient for its simplicity. It could be slightly more complete by explicitly referencing the singular spawn_agent alternative, but overall it provides all necessary operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero description coverage, so the description fully compensates. It explains that agents must be a list of objects with a 'prompt' entry and provides a concrete example, which is much richer than the bare schema definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Spawn multiple Codex agents in parallel,' which is a specific verb+resource statement. It clearly distinguishes itself from the sibling tool spawn_agent by emphasizing 'multiple' and 'in parallel'.

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 description implies use when multiple agents need to be spawned concurrently ('Spawn multiple Codex agents in parallel'), and the sibling context reinforces this. However, it does not explicitly state when not to use this tool or mention alternatives by name.

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/kky42/codex-as-mcp'

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