Skip to main content
Glama

claude_parallel

Execute multiple Claude AI tasks concurrently within a shared workspace, with results saved to a designated file for efficient batch processing.

Instructions

Run multiple claude tasks in parallel. All tasks share workspace/permission/save_file. Results are appended to save_file with XML wrappers (). Max 100 tasks. Model can be array: single element shared by all, or one per task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceYesProject root directory. Boundary for 'workspace-write'. Use absolute paths or relative paths.
permissionNoSecurity level: 'read-only' (analyze files), 'workspace-write' (modify inside workspace), 'unlimited' (full system access). Default: 'read-only'.read-only
save_fileYesPREFERRED when agent needs to write files or produce lengthy output. Output is written directly to this path, avoiding context overflow. This write is permitted even in read-only mode (server-handled). Essential for: code generation, detailed reports, documentation.
report_modeNoGenerate a standalone, document-style report (no chat filler) suitable for sharing.
context_pathsNoList of relevant files/dirs to preload as context hints.
modelNoModel override(s). If single element, all tasks use that model. If multiple elements, must match parallel_prompts length - each task uses corresponding model. Empty array uses CLI default.
system_promptNoComplete replacement for the default system prompt. Use only when you need full control over agent behavior. Prefer append_system_prompt for most cases.
append_system_promptNoAdditional instructions appended to the default system prompt. Recommended way to customize behavior. Example: 'Focus on performance optimization, avoid adding new dependencies'
agentNoSpecify an agent for the current session (overrides the default agent setting). Use predefined agent names configured in Claude Code settings.
parallel_promptsYesComplete prompts for parallel execution. Each spawns an independent subprocess.
parallel_task_notesYesLabels for each task. Length MUST equal parallel_prompts.
parallel_max_concurrencyNoMax concurrent subprocesses.
parallel_fail_fastNoStop spawning new tasks when any fails (already running tasks continue).
debugNoEnable execution stats (tokens, duration) for this call.
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: output format with XML wrappers, shared resource model, task limits, and model configuration options. It doesn't cover error handling, performance characteristics, or authentication needs, but provides substantial operational context for a complex parallel execution tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured in three sentences that cover purpose, output format, and key constraints. Each sentence adds value without redundancy. While dense, it's appropriately sized for a complex parallel execution tool with many parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 14-parameter tool with no annotations and no output schema, the description provides good operational context but lacks information about return values, error responses, or performance expectations. It covers the parallel execution model and output formatting well, but doesn't fully compensate for the missing structured metadata about this mutation-capable tool.

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?

With 100% schema description coverage, the schema already documents all 14 parameters thoroughly. The description adds minimal parameter-specific information beyond the schema, mentioning only that 'Model can be array: single element shared by all, or one per task' and output formatting details. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'Run multiple claude tasks in parallel' with specific details about shared resources and output format. It distinguishes from siblings like 'claude' (single task) and 'codex_parallel' (different model family), making the scope and differentiation explicit.

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 provides clear context for when to use this tool ('All tasks share workspace/permission/save_file') and mentions capacity limits ('Max 100 tasks'). However, it doesn't explicitly state when NOT to use it or name alternatives like 'claude' for single tasks, though the parallel nature is implied as the distinguishing factor.

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/shiharuharu/cli-agent-mcp'

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