Skip to main content
Glama

execute_swarm

Start a swarm run by providing a natural-language task; returns a run contract with wave summary and cost estimate or a budget preview. Supports multiple topologies like star or hierarchical.

Instructions

Start a swarm run; returns an immediate run contract (swarm_id, wave summary, cost estimate) or a budget preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesNatural-language task description (required). Use a plain quoted string — same shape as plan_task/decompose_task.
topologyNo
task_specNoOptional structured swarm payload (id, subtasks, complexity_score, …). When set, overrides task for planning/runtime handoff.
task_textNoAlias for task when callers use task_text instead of task.
max_agentsNo
budget_limitNo
urgency_hintNo
preview_tokenNo
workspace_rootNoWorkspace where declared subtask outputs are materialized. Defaults to the active MCP workspace.
unlimited_budgetNoDisable token budget circuit breaker and cost limit checks — swarm runs to completion regardless of token usage.
Behavior2/5

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

Lacks behavioral details beyond stating it starts a swarm run. With no annotations, the description should cover side effects, resource usage, or dependencies, which it does not.

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?

Single sentence, front-loaded with action and output summary, no redundancy. Could improve structure with bullet points.

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

Completeness2/5

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

For a tool with 10 parameters, nested objects, and no output schema, the description is too sparse. Fails to explain how parameters affect behavior or integrate with sibling tools.

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

Parameters2/5

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

Description adds no parameter meaning beyond the schema (50% coverage). Does not explain parameter roles or interactions.

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?

Clearly states it starts a swarm run and describes the immediate return format (run contract or budget preview), distinguishing it from sibling tools like inspect_swarm or start_task.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., start_task, plan_task). Does not mention prerequisites or exclusions.

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/timjensgrossinger/threnody'

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