Skip to main content

Why Multi-Agent Teams?

Single Agent Limitations:
  • Complex prompts become unwieldy (2000+ lines)
  • Hard to test and maintain
  • Generic responses for diverse tasks
Multi-Agent Benefits:
  • Specialization: Each agent focuses on one domain
  • Coordination: Coordinator delegates to specialists
  • Maintainability: Small, focused prompts
  • Testability: Test specialists independently

Team Structure

How It Works

1. User Reports Issue

2. Coordinator Analyzes & Delegates

3. Specialists Execute

4. Coordinator Synthesizes

Creating Teams

Via MCP Tools

The easiest way to create multi-agent teams:
Station uses these MCP tools: Example conversation:

Via .prompt File

The coordinator agent calls specialist agents as tools:

Creating Specialists

Specialists are regular agents focused on one domain:

Agent-as-Tool Naming

When an agent is used as a tool, its name becomes:
Example: “Kubernetes Expert” → __agent_kubernetes_expert

Best Practices

Each specialist should do one thing well. 5-8 tools max per specialist.
Coordinator prompts should clearly explain when to use each specialist.
Test each specialist before testing the full team.
Avoid coordinators calling other coordinators. Keep hierarchy flat.

Next Steps

Workflows

Orchestrate agents in durable pipelines with parallel execution

Evaluation

Test and score your agent teams

Bundles

Package teams for distribution