Skip to main content
Glama

Agent swarm (mixed Antigravity + Codex + Copilot + Cursor, parallel)

agent_swarm

Run multiple tasks in parallel across all supported AI backends, returning each answer in a labeled block and reporting failures individually. Use for simultaneous multi-agent queries.

Instructions

Run SEVERAL tasks IN PARALLEL across ALL backends in a single swarm.

Each task is its own worker and names the backend to run on, so one swarm can mix Antigravity (Gemini), Codex, Copilot, Cursor, and Grok workers — they run truly concurrently (capped at max_concurrency) and every answer comes back in one labelled block. A worker that fails is reported in place; the others still return.

SECURITY: this launches N unsandboxed agents at once — N times the prompt-injection surface of a single call (see the module SECURITY note). Only use it with trusted prompts on trusted content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYesOne object per parallel worker: - backend: "antigravity" (alias "agy"/"gemini"), "codex", "copilot" (alias "gh"/"github"), "cursor", or "grok" (alias "xai"; EXPERIMENTAL — see grok_ask) (required) - prompt: the question or instruction (required) - workspace: working dir for that worker (default: server cwd) - sandbox: "read-only" (default), "workspace-write", or "danger-full-access". Codex's is an enforced OS sandbox everywhere; Grok's is enforced on Linux/macOS only; Copilot's and Cursor's are agent/tool-level, not OS boundaries — see copilot_ask / cursor_ask / grok_ask. ANTIGRAVITY is the odd one: "read-only" maps to agy's plan mode (it investigates and writes a plan instead of editing files or running commands — see antigravity_ask's `plan`, and note it is agent-enforced, and needs agy 1.1.12+), "danger-full-access" states plainly that the worker is unrestricted, and "workspace-write" is REFUSED because agy has no write scoping to offer. Omitting it leaves an Antigravity worker unrestricted — that is the long-standing default, unlike every other backend here, so fence it explicitly if you want it fenced. - model: optional model override for ANY backend — Codex's `-m`, Copilot's/Cursor's `--model`, Grok's `-m`, or Antigravity's `--model` (an agy slug like "claude-sonnet-4-6"; validated against each backend's model list). Omit for each backend's default.
watchNoIf true, open the live "Agent Swarm" dashboard window (one row per worker, with a backend badge; click a row for its full step log).
timeout_sNoPer-worker timeout in seconds. Default 180.
max_concurrencyNoMax workers running at once (default 4). Higher = faster but more quota/rate-limit pressure and more agents at once.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses meaningful behavior beyond the annotations: workers run "truly concurrently," results return "in one labelled block," failed workers are "reported in place," and successful ones still return. The security warning about "N unsandboxed agents" and the prompt-injection surface adds important context that aligns with openWorldHint=true and readOnlyHint=false.

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 compact and well-structured: a front-loaded purpose statement, a brief explanation of worker behavior, and a clearly separated security warning. Every sentence earns its place and none merely repeats the schema.

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

Completeness5/5

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

For a complex, high-risk tool with an output schema and 100% schema coverage, the description covers the essential invocation context: parallel execution, backend mixing, failure behavior, concurrency cap, and security caveats. Nothing critical is missing for an agent to decide whether and how to call it.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds useful behavioral meaning for the tasks parameter — that each task is its own worker, names a backend, and can mix backends in one swarm — and clarifies that max_concurrency caps real parallelism. It does not add much on the other parameters, but the schema already documents them thoroughly.

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 specific verb and scope: "Run SEVERAL tasks IN PARALLEL across ALL backends in a single swarm." This clearly distinguishes agent_swarm from the single-backend sibling tools like antigravity_ask or codex_ask, and the title reinforces the mix of backends and parallel execution.

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 gives clear context for when to use the tool: multiple tasks, multiple backends, parallel execution. It also provides an explicit exclusion: "Only use it with trusted prompts on trusted content." However, it does not explicitly name single-task sibling tools as alternatives, leaving the when-not-to-use guidance slightly incomplete.

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/SinanTufekci/agent-intern'

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