Skip to main content
Glama

Agent swarm (mixed Antigravity + Codex, parallel)

agent_swarm

Execute tasks concurrently on both Antigravity and Codex backends, with each worker reporting its own output.

Instructions

Run SEVERAL tasks IN PARALLEL across BOTH 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) and Codex 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") or "codex" (required) - prompt: the question or instruction (required) - workspace: working dir for that worker (default: server cwd) - sandbox: Codex only — "read-only" (default), "workspace-write", or "danger-full-access". Ignored for Antigravity. - model: Codex only — model override (`-m`). Ignored for Antigravity.
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?

Annotations are sparse (readOnlyHint=false, openWorldHint=true). The description adds significant behavioral context: tasks run as independent workers with true concurrency capped by max_concurrency, failures are reported in place, and security implications of launching unsandboxed agents. No contradiction with annotations.

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?

Description is well-structured with bolded opening verb, bullet-point explanation, and security note. Slightly lengthy but justified by complexity. Front-loaded with core purpose.

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 tool's complexity (parallel, mixed backends) and the presence of output schema and full parameter descriptions, the description is fully adequate. It covers behavior, security, and ties to sibling tools.

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 coverage is 100% with detailed parameter descriptions. The description summarizes but does not add extra meaning beyond the schema. Baseline 3 applies per guidelines.

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 it runs several tasks in parallel across both Antigravity and Codex backends. It distinguishes from sibling tools like antigravity_ask or codex_ask which are single-call tools.

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 includes a security warning advising use only with trusted prompts on trusted content, implying when not to use. It lacks explicit alternatives but the context implies for parallel mixed-backend tasks.

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