Skip to main content
Glama

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

agent_swarm

Execute several tasks in parallel across Antigravity, Codex, Copilot, and Cursor backends, with results returned in a single labelled response.

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, and Cursor 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"), or "cursor" (required) - prompt: the question or instruction (required) - workspace: working dir for that worker (default: server cwd) - sandbox: Codex/Copilot/Cursor only — "read-only" (default), "workspace-write", or "danger-full-access". Ignored for Antigravity. (Codex's is an enforced OS sandbox; Copilot's and Cursor's are agent/tool-level, not OS boundaries — see copilot_ask / cursor_ask.) - model: optional model override for ANY backend — Codex's `-m`, Copilot's/Cursor's `--model`, 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?

Discloses concurrency behavior (capped at max_concurrency), failure handling (failing worker reported in place, others proceed), and security risks (N unsandboxed agents at once), adding context beyond the annotations.

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?

Front-loaded with core purpose, followed by task structure, concurrency details, and security warning. Every sentence is necessary and well-organized.

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?

Given the presence of an output schema, the description covers all necessary aspects: purpose, parameters, behavior, and security, leaving no gaps.

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%, so baseline is 3. Description adds some context (e.g., backend aliases) but mostly restates schema information.

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 runs several tasks in parallel across multiple backends, which distinguishes it from single-backend sibling tools like antigravity_ask or codex_ask.

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?

Explicitly explains when to use (parallel multi-backend tasks) and when not (untrusted prompts due to increased injection surface), with alternatives implied by sibling tool list.

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