Skip to main content
Glama

call_agents_batch

Run multiple agents concurrently and wait until all finish, providing all results together for scenarios where you need every output before taking the next step.

Instructions

Execute multiple agents in PARALLEL (BLOCKING until ALL complete).

⚠️ Usually NOT what you want

Prefer call_agent_async × N instead:

  • Async returns immediately, you can continue working

  • Batch blocks until the SLOWEST agent finishes

  • If one agent takes 2min, you wait 2min doing nothing

Only use batch when:

  • You MUST have ALL results before ANY next step

  • Results are interdependent (rare)

  • You're okay blocking for potentially minutes

Example (usually wrong):

{ "calls": [{ "agent": "explore", ... }, { "agent": "researcher", ... }] }

↑ This blocks until both finish. Use call_agent_async × 2 instead.

Example (correct use case): Comparing outputs from multiple agents where you need all results simultaneously.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdYesWorking directory for all agents (required)
callsYesArray of agent calls to execute in parallel (1-10 calls)
Behavior4/5

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

With no annotations, the description carries the transparency burden. It fully discloses blocking behavior, parallel execution, and the risk of waiting for the slowest agent. It doesn't cover failure modes or return details, but core behavioral traits are clearly communicated.

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 longer than ideal but well-structured with headings and examples. The warning section is impactful, and the examples illustrate misuse and correct use. However, it could be tightened without losing value.

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 tool with no output schema, the description explains blocking semantics, parallel execution, and appropriate use cases. It doesn't describe the return value format or how to retrieve individual results (though sibling get_agent_result exists), which keeps it from being fully complete.

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?

Input schema describes both cwd and calls with 100% coverage, so the baseline is 3. The description's example adds a concrete JSON structure showing the calls array shape, but doesn't explain parameters beyond the schema. Reasonable but not exceptional.

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 a clear verb+resource statement: 'Execute multiple agents in PARALLEL (BLOCKING until ALL complete).' It explicitly distinguishes itself from call_agent_async, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly advises against typical use, names the preferred alternative (call_agent_async × N), and lists precise conditions where batch is appropriate. This is outstanding when-to-use guidance.

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/J3n5en/impart-mcp'

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